hg clone -r mybranch from two repos in sync leads to two different revisions

Dario Sestito darios at symbian.org
Fri Jan 15 08:55:00 CST 2010

hope you can help me, I would like to understand if this is the intended
behaviour for Mercurial or if I should raise a bug. If this is the intended
behaviour I wouldn't mind understanding why :-)

Let repo1 and repo2 be two clones of the same repository that now and then I
keep in sync with pull/push.
I've noticed that running:

hg clone repo1 -r branch


hg clone repo2 -r branch

could lead to two different revisions even if repo1 and repo2 are in sync
(i.e. hg -r repo1 incoming/outgoing repo2 shows nothing)

Reason for this as far as I understand is that -r branch doesn't point to
the last (chronologically) submitted changeset, but to the revision that was
committed/pushed/pulled later to that particular clone of the repository.

So my question is is this really intended, why not having -r branch pointing
to the last (chronologically) submitted changeset, regardless of when it was
added to the clone (i.e. regardless of the revision number)?

thanks in advance

View this message in context: http://old.nabble.com/hg-clone--r-mybranch-from-two-repos-in-sync-leads-to-two-different-revisions-tp27178299p27178299.html
Sent from the Mercurial mailing list archive at Nabble.com.

More information about the Mercurial mailing list