[Bug 3837] New: committing divergent head on closed branch should say it's reopening the branch

mercurial-bugs at selenic.com mercurial-bugs at selenic.com
Fri Feb 22 05:17:46 CST 2013


http://bz.selenic.com/show_bug.cgi?id=3837

          Priority: normal
            Bug ID: 3837
                CC: mercurial-devel at selenic.com
          Assignee: bugzilla at selenic.com
           Summary: committing divergent head on closed branch should say
                    it's reopening the branch
          Severity: bug
    Classification: Unclassified
                OS: Mac OS
          Reporter: kbullock+mercurial at ringworld.org
          Hardware: PC
            Status: UNCONFIRMED
           Version: 2.5
         Component: Mercurial
           Product: Mercurial

Going from 0 -> 1 open heads on a branch doesn't print a message to that
effect, if you don't commit on top of the --close-branch commit:

$ hg init a
$ cd a
$ echo a>a
$ hg ci -Am0
adding a
$ hg ci --close-branch -m'1 (close branch)'
$ hg up 0
0 files updated, 0 files merged, 0 files removed, 0 files unresolved
$ hg heads
$ echo b>a
$ hg ci -m2
$ 

Here I would expect to see the message 'reopening closed branch head' or
something similar (maybe just 'reopening closed branch "default"').

-- 
You are receiving this mail because:
You are on the CC list for the bug.


More information about the Mercurial-devel mailing list