Any way to relate repos w/o cloning?

[Chris Stromberger]

On Thu, Nov 13, 2008 at 10:25 AM, Ted Pavlic <ted at tedpavlic.com> wrote:

>    You still should be able to "pull -f", this will create another head
>>    in your repository, and then, once merge, you should be able to push
>>    to your colleague ...
>>
>> Aha!  I guess I should have tried "hg help pull" first :).  So, I did
>> this, and the pull worked (did not have errors).  But one question now.  I
>> know that there are changes in the files in the repo I pulled from, but when
>> I do "hg st" in the recipient directory, no changes are reported.  Since the
>> repo pulled from that changed repo, shouldn't "hg st" report those
>> differences in my current repo?
>>
>
> First: By itself, pulling doesn't change the working directory. That is,
> you need to "hg update" after the pull in order to get the working directory
> in sync with the new tip (note: an "hg merge" might be required here; after
> the merge, you'll have to check in the resulting working directory as a new
> changeset).
>
> Second: "hg status" detects whether the working directory has changed with
> respect to the repo. Doing an "hg pull" followed by an "hg update" will not
> cause "hg status" to report any change because the working directory will be
> in sync with an existing changeset.



Yes, but if I do the pull without doing an update, shouldn't hg st report
the updates that would occur in the working dir when I do an update?

Does it have something to do with the multiple heads??  Here's the output
from hg heads:

changeset:   1:ec46614b071e
tag:         tip
parent:      -1:000000000000
user:        cstromberger
date:        Thu Nov 13 07:13:24 2008 -0800
summary:     Initial import

changeset:   0:cc98724a0a7a
user:        cstromberger
date:        Thu Nov 13 08:11:06 2008 -0800
summary:     Initial import
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://selenic.com/pipermail/mercurial/attachments/20081113/40b07672/attachment.htm