diff contrib/memory.py @ 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 08a0f04b56bd
children 3e0d27d298b7
line wrap: on
line diff