view setup.cfg @ 4991:2928f35023a1 stable

evolve: make sure divergence resolution doesn't undo changes (issue6203)

Before this patch, in content-divergence resolution logic if resolution
parent is not the parent of any of the two divergent changesets then
it could undo some changes introduced by previous revs (while resolving
stack of content-divergent changesets) as demonstrated by the test added in
previous patch.

To solve this, what this patch doing is: if divergent cset has obsolete
parent with a successor then first resolve the "orphan" instability  of
divergent cset by relocating, then perform the content-divergence resolution.

After this change in logic, I found that it's kind of more correct as
reflected by the changes in tests/test-evolve-content-divergent-corner-cases.t
where it prevented creating conflicts while merging.

Changes in tests/test-evolve-content-divergent-stack.t demonstrate the fixed
behaviour.

Next patches will be covering the `evolve --continue` case for the relocation
of "divergent" cset.

[flake8]
ignore =
         #closing bracket does not match indentation of opening bracket's line
         E123,
         # closing bracket does not match visual indentation
         E124,
         # visually indented line with same indent as next logical line
         E129,
         # at least two spaces before inline comment
         E261,
         # too many leading '#' for block comment
         E266,
         # expected 2 blank lines, found 0
         E302,
         # expected 2 blank lines after end of function or class
         E305,
         # module level import not at top of file
         E402,
         # line too long (82 > 79 characters)
         E501,
         # do not assign a lambda expression, use a def
         E731,
         # class names should use CapWords convention
         N801,
         # line break occurred before a binary operator
         W503
builtins=xrange, execfile