Is there any situation when closing a head in the default branch is recommended?
Kent Larsson
kent.larsson at gmail.com
Tue Aug 30 10:36:29 UTC 2011
Hi!
Is there any situation when closing a head in the default branch is
recommended?
I am asking as one of the developers in our team had two heads in default,
one of them was just a test but there were a couple of commits in that
branch (so doing a rollback wasn't possible).
I (falsely) thought that closing the dead end branch head of default would
make it possible to push without any problem. I should have taken the hint
when I had to force the push. It turns out that the dead end head of default
was the latest one commited in his repository, to my surprise it became the
new tip when another developer pulled. I was under the false assumption that
the closed head wouldn't become the tip as it was marked as closed.
So my question is. Is there any situation when one wants to close a dead end
branch within a named branch?
And is the correct way to merge the dead end head with the one we like to
use and not merge in any changes from the dead end head?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mercurial-scm.org/pipermail/mercurial/attachments/20110830/52df8264/attachment-0002.html>
More information about the Mercurial
mailing list