[BUG] "hg clone -r branchname" incorrectly sets working branch
Leo Razoumov
slonik.az at gmail.com
Wed Jun 18 16:19:13 CDT 2008
On 6/18/08, Dirkjan Ochtman <dirkjan at ochtman.nl> wrote:
>
> Please file a bug (find the bts from the wiki homepage).
>
> Cheers,
>
> Dirkjan
>
Dirkjan,
apparently the bug is worse than I thought. In Mercurial 1.0.1 "hg
clone --rev=123" sets your working directory to the latest revision on
the *default* branch even if it is different from 123. This happens if
revision 123 has a misfortune to reside on a non-default branch. One
has to explicitly issue a second command "hg upd 123" to get sync the
working dir. I just sent another message to the list about it.
Unfortunately, I cannot file a bug report because selenic bug tracker
requires login and I do not have one.
--Leo--
More information about the Mercurial
mailing list