diff mercurial/help/revisions.txt @ 20245:4edd179fefb8

help: branch names primarily denote the tipmost unclosed branch head Was the behavior correct and the description wrong so it should be updated as in this patch? Or should the code work as the documentation says? Both ways could make some sense ... but none of them are obvious in all cases. One place where it currently cause problems is when the current revision has another branch head that is closer to tip but closed. 'hg rebase' refuses to rebase to that as it only see the tip-most unclosed branch head which is the current revision. /me kind of likes named branches, but no so much how branch closing works ...
author Mads Kiilerich <madski@unity3d.com>
date Thu, 21 Nov 2013 15:17:18 -0500
parents 43cfe56121d3
children bbb5cc55ab8b
line wrap: on
line diff
--- a/mercurial/help/revisions.txt	Sun Jan 12 23:28:21 2014 +0100
+++ b/mercurial/help/revisions.txt	Thu Nov 21 15:17:18 2013 -0500
@@ -14,9 +14,9 @@
 
 Any other string is treated as a bookmark, tag, or branch name. A
 bookmark is a movable pointer to a revision. A tag is a permanent name
-associated with a revision. A branch name denotes the tipmost revision
-of that branch. Bookmark, tag, and branch names must not contain the ":"
-character.
+associated with a revision. A branch name denotes the tipmost open branch head
+of that branch - or if they are all closed, the tipmost closed head of the
+branch. Bookmark, tag, and branch names must not contain the ":" character.
 
 The reserved name "tip" always identifies the most recent revision.