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

[Martin Geisler]

Thomas Lehmann <Iris-und-Thomas-Lehmann at T-Online.de> writes:

>> 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.
>> From the documentation I didn't got the correct way to do this. Of
>> course I will continue searching in your documentation (also I will
>> buy this book); but could you please help this time?
>
> Well, one point I got is that "pull" does expect a revision. (is
> working - of course) But this is the problem I have. When committing I
> may deliver also files not being part of the path I would like to
> transfer to another repository. When using a revision I can not say:
> "use this path only" (can I?)

You cannot push/pull only a subdirectory with Mercurial, you must always
push/pull files from the entire project. You can choose which revisions
to pull (as you noticed above) but revisions effect the entire project.

This is unlike a system like Subversion where you can do a checkout of a
subdirectory and commit changes to this subdirectory.

It is therefore recommended that you create a repository per project,
instead of having just one "super-repository" like people sometimes to
with Subversion.

-- 
Martin Geisler

VIFF (Virtual Ideal Functionality Framework) brings easy and efficient
SMPC (Secure Multiparty Computation) to Python. See: http://viff.dk/.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 196 bytes
Desc: not available
Url : http://selenic.com/pipermail/mercurial/attachments/20090904/d70317a4/attachment.pgp