https://bz.mercurial-scm.org/show_bug.cgi?id=6889
Bug ID: 6889
Summary: Unclear how to tell in advance where plain `hg update'
will send you or how to go back
Product: Mercurial
Version: 6.7.4
Hardware: PC
OS: NetBSD
Status: UNCONFIRMED
Severity: feature
Priority: wish
Component: Mercurial
Assignee: bugzi...@mercurial-scm.org
Reporter: mercurial-bugzi...@campbell.mumble.net
CC: mercurial-de...@mercurial-scm.org
Python Version: ---
`hg update' (with no [-r] REV argument) will pick some reasonable choice of
changeset to update to.
But it's not clear how to tell in advance what changeset that will be,
particularly if there's multiple heads and topics involved.
And if I do that and find it's not where I wanted to go, but I didn't record in
advance what `hg parent' or `hg log -r .' or whatever said, it's not clear how
to go back to the state I was in before.
Is there a way to make `hg update' do a dry run and print what it would update
to (and whether there are any uncommitted changes that would have to be
merged), without actually changing any state?
Failing that, is there a way to reverse the effect of `hg update' and go back
to the changeset I was at before?
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
Mercurial-devel mailing list
Mercurial-devel@lists.mercurial-scm.org
https://lists.mercurial-scm.org/mailman/listinfo/mercurial-devel
