Inter-Repository work.... (new to mercurial)

[Thomas Lehmann]

> Welcome!
Thanks!

> First, have you read
> http://hgbook.red-bean.com/read/collaborating-with-other-people.html ?
>  (Or bought the book, since it has been published recently.)
No I have not been reading this!
I will buy this!

> Second, the simple answer is "push or pull".  But that might not be
> the answer you're looking for, since I don't entirely understand your
> question: in particular, what do you mean by "whole versions of a part
> of [your] repository"?  Remember, Mercurial tracks a whole filesystem
> tree atomically.  It's generally frowned upon to pick up patches to
> part of the tree and apply them separately from the rest of the tree.
> It's not impossible, it's just not the normal way of working.
>
> You'll need to clarify your question.

I have been assuming that this is the point: "push or pull"
I have a repository with a structure like this: (three paths as
example)

D:\MercurialRepository\xml
D:\MercurialRepository\python
D:\MercurialRepository\python\tests
D:\MercurialRepository\python\tkinter

Now I want to "copy" all version of all files of last path into the
empty repository
from bitpucket. One Idea was to say:

being at D:\XmlBasedGuiDesign (this is the clone of the bitbucket
repository)

hg pull D:\MercurialRepository\python\tkinter
abort: repository D:\MercurialRepository\python\tkinter not found!

Well, yes that's true. The ".hg" is only at D:\MercurialRepository.