[Bug 4015] New: Moving a bookmark to the successor of an obsolete change shouldn't require --force
mercurial-bugs at selenic.com
mercurial-bugs at selenic.com
Fri Aug 9 23:45:47 UTC 2013
http://bz.selenic.com/show_bug.cgi?id=4015
Priority: normal
Bug ID: 4015
CC: mercurial-devel at selenic.com
Assignee: bugzilla at selenic.com
Summary: Moving a bookmark to the successor of an obsolete
change shouldn't require --force
Severity: bug
Classification: Unclassified
OS: Mac OS
Reporter: durin42 at gmail.com
Hardware: PC
Status: UNCONFIRMED
Version: unspecified
Component: Mercurial
Product: Mercurial
I pulled a revised version of some changes from smf, and when I did so I had to
use --force to move @ to the revision I got from him.
I think that when advancing a bookmark, the set successors($MARKED_REV)::
should be valid without force.
--
You are receiving this mail because:
You are on the CC list for the bug.
More information about the Mercurial-devel
mailing list