[issue2473] Backout works like commit with inverted changes, not like intuitive backout.
bugs at mercurial.selenic.com
Wed Nov 3 07:05:00 CDT 2010
New submission from Yury <razoomnick at mail.ru>:
Backout works like commit with inverted changes, not like intuitive backout.
An example of working in this way that makes troubles:
I have a branch named "Test". I made some changes to my project and
committed them with comment "Flags integration iteration". Then I decide
that flags integration would take more time and would be better to develop
it in separate branch. I backed out "Flags integration iteration" changeset
and committed my version as branch named "Flags". All was fine till I
finished working with Flags branch and merged it to Test branch. After
merging some changes of "Flags integration iteration" were missed because
were reverted in newer revision (backout).
So, I think, would be better implement backout as "true backout", not as
commit with inverted changes.
title: Backout works like commit with inverted changes, not like intuitive backout.
Mercurial issue tracker <bugs at mercurial.selenic.com>
More information about the Mercurial-devel