merge: consider the file merged when using :merge-{local,other}

Returning `None` from `simplemerge()` means that the caller interprets
it as "no merge was necessary (because two sides matched)". See
6217040b2780 and issue2680 for some background. However,
`simplemerge()` shouldn't even get called in such scenarios, and
returning `None` means that the file is not considered merged, even
though the contents actually were. See the affected test cases.

Differential Revision: https://phab.mercurial-scm.org/D11999

mercurial/simplemerge.py

@@ -1,515 +1,514 b''
 # Copyright (C) 2004, 2005 Canonical Ltd
 #
 # This program is free software; you can redistribute it and/or modify
 # it under the terms of the GNU General Public License as published by
 # the Free Software Foundation; either version 2 of the License, or
 # (at your option) any later version.
 #
 # This program is distributed in the hope that it will be useful,
 # but WITHOUT ANY WARRANTY; without even the implied warranty of
 # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
 # GNU General Public License for more details.
 #
 # You should have received a copy of the GNU General Public License
 # along with this program; if not, see <http://www.gnu.org/licenses/>.
 
 # mbp: "you know that thing where cvs gives you conflict markers?"
 # s: "i hate that."
 
 from __future__ import absolute_import
 
 from .i18n import _
 from . import (
     error,
     mdiff,
     pycompat,
 )
 from .utils import stringutil
 
 
 def intersect(ra, rb):
     """Given two ranges return the range where they intersect or None.
 
     >>> intersect((0, 10), (0, 6))
     (0, 6)
     >>> intersect((0, 10), (5, 15))
     (5, 10)
     >>> intersect((0, 10), (10, 15))
     >>> intersect((0, 9), (10, 15))
     >>> intersect((0, 9), (7, 15))
     (7, 9)
     """
     assert ra[0] <= ra[1]
     assert rb[0] <= rb[1]
 
     sa = max(ra[0], rb[0])
     sb = min(ra[1], rb[1])
     if sa < sb:
         return sa, sb
     else:
         return None
 
 
 def compare_range(a, astart, aend, b, bstart, bend):
     """Compare a[astart:aend] == b[bstart:bend], without slicing."""
     if (aend - astart) != (bend - bstart):
         return False
     for ia, ib in zip(
         pycompat.xrange(astart, aend), pycompat.xrange(bstart, bend)
     ):
         if a[ia] != b[ib]:
             return False
     else:
         return True
 
 
 class Merge3Text(object):
     """3-way merge of texts.
 
     Given strings BASE, OTHER, THIS, tries to produce a combined text
     incorporating the changes from both BASE->OTHER and BASE->THIS."""
 
     def __init__(self, basetext, atext, btext, base=None, a=None, b=None):
         self.basetext = basetext
         self.atext = atext
         self.btext = btext
         if base is None:
             base = mdiff.splitnewlines(basetext)
         if a is None:
             a = mdiff.splitnewlines(atext)
         if b is None:
             b = mdiff.splitnewlines(btext)
         self.base = base
         self.a = a
         self.b = b
 
     def merge_groups(self):
         """Yield sequence of line groups.  Each one is a tuple:
 
         'unchanged', lines
              Lines unchanged from base
 
         'a', lines
              Lines taken from a
 
         'same', lines
              Lines taken from a (and equal to b)
 
         'b', lines
              Lines taken from b
 
         'conflict', (base_lines, a_lines, b_lines)
              Lines from base were changed to either a or b and conflict.
         """
         for t in self.merge_regions():
             what = t[0]
             if what == b'unchanged':
                 yield what, self.base[t[1] : t[2]]
             elif what == b'a' or what == b'same':
                 yield what, self.a[t[1] : t[2]]
             elif what == b'b':
                 yield what, self.b[t[1] : t[2]]
             elif what == b'conflict':
                 yield (
                     what,
                     (
                         self.base[t[1] : t[2]],
                         self.a[t[3] : t[4]],
                         self.b[t[5] : t[6]],
                     ),
                 )
             else:
                 raise ValueError(what)
 
     def merge_regions(self):
         """Return sequences of matching and conflicting regions.
 
         This returns tuples, where the first value says what kind we
         have:
 
         'unchanged', start, end
              Take a region of base[start:end]
 
         'same', astart, aend
              b and a are different from base but give the same result
 
         'a', start, end
              Non-clashing insertion from a[start:end]
 
         'conflict', zstart, zend, astart, aend, bstart, bend
             Conflict between a and b, with z as common ancestor
 
         Method is as follows:
 
         The two sequences align only on regions which match the base
         and both descendants.  These are found by doing a two-way diff
         of each one against the base, and then finding the
         intersections between those regions.  These "sync regions"
         are by definition unchanged in both and easily dealt with.
 
         The regions in between can be in any of three cases:
         conflicted, or changed on only one side.
         """
 
         # section a[0:ia] has been disposed of, etc
         iz = ia = ib = 0
 
         for region in self.find_sync_regions():
             zmatch, zend, amatch, aend, bmatch, bend = region
             # print 'match base [%d:%d]' % (zmatch, zend)
 
             matchlen = zend - zmatch
             assert matchlen >= 0
             assert matchlen == (aend - amatch)
             assert matchlen == (bend - bmatch)
 
             len_a = amatch - ia
             len_b = bmatch - ib
             len_base = zmatch - iz
             assert len_a >= 0
             assert len_b >= 0
             assert len_base >= 0
 
             # print 'unmatched a=%d, b=%d' % (len_a, len_b)
 
             if len_a or len_b:
                 # try to avoid actually slicing the lists
                 equal_a = compare_range(
                     self.a, ia, amatch, self.base, iz, zmatch
                 )
                 equal_b = compare_range(
                     self.b, ib, bmatch, self.base, iz, zmatch
                 )
                 same = compare_range(self.a, ia, amatch, self.b, ib, bmatch)
 
                 if same:
                     yield b'same', ia, amatch
                 elif equal_a and not equal_b:
                     yield b'b', ib, bmatch
                 elif equal_b and not equal_a:
                     yield b'a', ia, amatch
                 elif not equal_a and not equal_b:
                     yield b'conflict', iz, zmatch, ia, amatch, ib, bmatch
                 else:
                     raise AssertionError(b"can't handle a=b=base but unmatched")
 
                 ia = amatch
                 ib = bmatch
             iz = zmatch
 
             # if the same part of the base was deleted on both sides
             # that's OK, we can just skip it.
 
             if matchlen > 0:
                 assert ia == amatch
                 assert ib == bmatch
                 assert iz == zmatch
 
                 yield b'unchanged', zmatch, zend
                 iz = zend
                 ia = aend
                 ib = bend
 
     def find_sync_regions(self):
         """Return a list of sync regions, where both descendants match the base.
 
         Generates a list of (base1, base2, a1, a2, b1, b2).  There is
         always a zero-length sync region at the end of all the files.
         """
 
         ia = ib = 0
         amatches = mdiff.get_matching_blocks(self.basetext, self.atext)
         bmatches = mdiff.get_matching_blocks(self.basetext, self.btext)
         len_a = len(amatches)
         len_b = len(bmatches)
 
         sl = []
 
         while ia < len_a and ib < len_b:
             abase, amatch, alen = amatches[ia]
             bbase, bmatch, blen = bmatches[ib]
 
             # there is an unconflicted block at i; how long does it
             # extend?  until whichever one ends earlier.
             i = intersect((abase, abase + alen), (bbase, bbase + blen))
             if i:
                 intbase = i[0]
                 intend = i[1]
                 intlen = intend - intbase
 
                 # found a match of base[i[0], i[1]]; this may be less than
                 # the region that matches in either one
                 assert intlen <= alen
                 assert intlen <= blen
                 assert abase <= intbase
                 assert bbase <= intbase
 
                 asub = amatch + (intbase - abase)
                 bsub = bmatch + (intbase - bbase)
                 aend = asub + intlen
                 bend = bsub + intlen
 
                 assert self.base[intbase:intend] == self.a[asub:aend], (
                     self.base[intbase:intend],
                     self.a[asub:aend],
                 )
 
                 assert self.base[intbase:intend] == self.b[bsub:bend]
 
                 sl.append((intbase, intend, asub, aend, bsub, bend))
 
             # advance whichever one ends first in the base text
             if (abase + alen) < (bbase + blen):
                 ia += 1
             else:
                 ib += 1
 
         intbase = len(self.base)
         abase = len(self.a)
         bbase = len(self.b)
         sl.append((intbase, intbase, abase, abase, bbase, bbase))
 
         return sl
 
 
 def _verifytext(text, path, ui, opts):
     """verifies that text is non-binary (unless opts[text] is passed,
     then we just warn)"""
     if stringutil.binary(text):
         msg = _(b"%s looks like a binary file.") % path
         if not opts.get('quiet'):
             ui.warn(_(b'warning: %s\n') % msg)
         if not opts.get('text'):
             raise error.Abort(msg)
     return text
 
 
 def _picklabels(overrides):
     if len(overrides) > 3:
         raise error.Abort(_(b"can only specify three labels."))
     result = [None, None, None]
     for i, override in enumerate(overrides):
         result[i] = override
     return result
 
 
 def _detect_newline(m3):
     if len(m3.a) > 0:
         if m3.a[0].endswith(b'\r\n'):
             return b'\r\n'
         elif m3.a[0].endswith(b'\r'):
             return b'\r'
     return b'\n'
 
 
 def _minimize(a_lines, b_lines):
     """Trim conflict regions of lines where A and B sides match.
 
     Lines where both A and B have made the same changes at the beginning
     or the end of each merge region are eliminated from the conflict
     region and are instead considered the same.
     """
     alen = len(a_lines)
     blen = len(b_lines)
 
     # find matches at the front
     ii = 0
     while ii < alen and ii < blen and a_lines[ii] == b_lines[ii]:
         ii += 1
     startmatches = ii
 
     # find matches at the end
     ii = 0
     while ii < alen and ii < blen and a_lines[-ii - 1] == b_lines[-ii - 1]:
         ii += 1
     endmatches = ii
 
     lines_before = a_lines[:startmatches]
     new_a_lines = a_lines[startmatches : alen - endmatches]
     new_b_lines = b_lines[startmatches : blen - endmatches]
     lines_after = a_lines[alen - endmatches :]
     return lines_before, new_a_lines, new_b_lines, lines_after
 
 
 def render_minimized(
     m3,
     name_a=None,
     name_b=None,
     start_marker=b'<<<<<<<',
     mid_marker=b'=======',
     end_marker=b'>>>>>>>',
 ):
     """Return merge in cvs-like form."""
     newline = _detect_newline(m3)
     conflicts = False
     if name_a:
         start_marker = start_marker + b' ' + name_a
     if name_b:
         end_marker = end_marker + b' ' + name_b
     merge_groups = m3.merge_groups()
     lines = []
     for what, group_lines in merge_groups:
         if what == b'conflict':
             conflicts = True
             base_lines, a_lines, b_lines = group_lines
             minimized = _minimize(a_lines, b_lines)
             lines_before, a_lines, b_lines, lines_after = minimized
             lines.extend(lines_before)
             lines.append(start_marker + newline)
             lines.extend(a_lines)
             lines.append(mid_marker + newline)
             lines.extend(b_lines)
             lines.append(end_marker + newline)
             lines.extend(lines_after)
         else:
             lines.extend(group_lines)
     return lines, conflicts
 
 
 def render_merge3(m3, name_a, name_b, name_base):
     """Render conflicts as 3-way conflict markers."""
     newline = _detect_newline(m3)
     conflicts = False
     lines = []
     for what, group_lines in m3.merge_groups():
         if what == b'conflict':
             base_lines, a_lines, b_lines = group_lines
             conflicts = True
             lines.append(b'<<<<<<< ' + name_a + newline)
             lines.extend(a_lines)
             lines.append(b'||||||| ' + name_base + newline)
             lines.extend(base_lines)
             lines.append(b'=======' + newline)
             lines.extend(b_lines)
             lines.append(b'>>>>>>> ' + name_b + newline)
         else:
             lines.extend(group_lines)
     return lines, conflicts
 
 
 def render_mergediff(m3, name_a, name_b, name_base):
     """Render conflicts as conflict markers with one snapshot and one diff."""
     newline = _detect_newline(m3)
     lines = []
     conflicts = False
     for what, group_lines in m3.merge_groups():
         if what == b'conflict':
             base_lines, a_lines, b_lines = group_lines
             base_text = b''.join(base_lines)
             b_blocks = list(
                 mdiff.allblocks(
                     base_text,
                     b''.join(b_lines),
                     lines1=base_lines,
                     lines2=b_lines,
                 )
             )
             a_blocks = list(
                 mdiff.allblocks(
                     base_text,
                     b''.join(a_lines),
                     lines1=base_lines,
                     lines2=b_lines,
                 )
             )
 
             def matching_lines(blocks):
                 return sum(
                     block[1] - block[0]
                     for block, kind in blocks
                     if kind == b'='
                 )
 
             def diff_lines(blocks, lines1, lines2):
                 for block, kind in blocks:
                     if kind == b'=':
                         for line in lines1[block[0] : block[1]]:
                             yield b' ' + line
                     else:
                         for line in lines1[block[0] : block[1]]:
                             yield b'-' + line
                         for line in lines2[block[2] : block[3]]:
                             yield b'+' + line
 
             lines.append(b"<<<<<<<" + newline)
             if matching_lines(a_blocks) < matching_lines(b_blocks):
                 lines.append(b"======= " + name_a + newline)
                 lines.extend(a_lines)
                 lines.append(b"------- " + name_base + newline)
                 lines.append(b"+++++++ " + name_b + newline)
                 lines.extend(diff_lines(b_blocks, base_lines, b_lines))
             else:
                 lines.append(b"------- " + name_base + newline)
                 lines.append(b"+++++++ " + name_a + newline)
                 lines.extend(diff_lines(a_blocks, base_lines, a_lines))
                 lines.append(b"======= " + name_b + newline)
                 lines.extend(b_lines)
             lines.append(b">>>>>>>" + newline)
             conflicts = True
         else:
             lines.extend(group_lines)
     return lines, conflicts
 
 
 def _resolve(m3, sides):
     lines = []
     for what, group_lines in m3.merge_groups():
         if what == b'conflict':
             for side in sides:
                 lines.extend(group_lines[side])
         else:
             lines.extend(group_lines)
     return lines
 
 
 def simplemerge(ui, localctx, basectx, otherctx, **opts):
     """Performs the simplemerge algorithm.
 
     The merged result is written into `localctx`.
     """
 
     def readctx(ctx):
         # Merges were always run in the working copy before, which means
         # they used decoded data, if the user defined any repository
         # filters.
         #
         # Maintain that behavior today for BC, though perhaps in the future
         # it'd be worth considering whether merging encoded data (what the
         # repository usually sees) might be more useful.
         return _verifytext(ctx.decodeddata(), ctx.path(), ui, opts)
 
     try:
         localtext = readctx(localctx)
         basetext = readctx(basectx)
         othertext = readctx(otherctx)
     except error.Abort:
-        return 1
+        return True
 
     m3 = Merge3Text(basetext, localtext, othertext)
     conflicts = False
     mode = opts.get('mode', b'merge')
     if mode == b'union':
         lines = _resolve(m3, (1, 2))
     elif mode == b'local':
         lines = _resolve(m3, (1,))
     elif mode == b'other':
         lines = _resolve(m3, (2,))
     else:
         name_a, name_b, name_base = _picklabels(opts.get('label', []))
         if mode == b'mergediff':
             lines, conflicts = render_mergediff(m3, name_a, name_b, name_base)
         elif mode == b'merge3':
             lines, conflicts = render_merge3(m3, name_a, name_b, name_base)
         else:
             lines, conflicts = render_minimized(m3, name_a, name_b)
 
     mergedtext = b''.join(lines)
     if opts.get('print'):
         ui.fout.write(mergedtext)
     else:
         # localctx.flags() already has the merged flags (done in
         # mergestate.resolve())
         localctx.write(mergedtext, localctx.flags())
 
-    if conflicts:
-        return 1
+    return conflicts

tests/test-annotate.t

@@ -1,1202 +1,1202 b''
   $ cat >> "$HGRCPATH" << EOF
   > [ui]
   > merge = :merge3
   > EOF
 
 init
 
   $ hg init repo
   $ cd repo
 
 commit
 
   $ echo 'a' > a
   $ hg ci -A -m test -u nobody -d '1 0'
   adding a
 
 annotate -c
 
   $ hg annotate -c a
   8435f90966e4: a
 
 annotate -cl
 
   $ hg annotate -cl a
   8435f90966e4:1: a
 
 annotate -d
 
   $ hg annotate -d a
   Thu Jan 01 00:00:01 1970 +0000: a
 
 annotate -n
 
   $ hg annotate -n a
   0: a
 
 annotate -nl
 
   $ hg annotate -nl a
   0:1: a
 
 annotate -u
 
   $ hg annotate -u a
   nobody: a
 
 annotate -cdnu
 
   $ hg annotate -cdnu a
   nobody 0 8435f90966e4 Thu Jan 01 00:00:01 1970 +0000: a
 
 annotate -cdnul
 
   $ hg annotate -cdnul a
   nobody 0 8435f90966e4 Thu Jan 01 00:00:01 1970 +0000:1: a
 
 annotate (JSON)
 
   $ hg annotate -Tjson a
   [
    {
     "lines": [{"line": "a\n", "rev": 0}],
     "path": "a"
    }
   ]
 
   $ hg annotate -Tjson -cdfnul a
   [
    {
     "lines": [{"date": [1.0, 0], "line": "a\n", "lineno": 1, "node": "8435f90966e442695d2ded29fdade2bac5ad8065", "path": "a", "rev": 0, "user": "nobody"}],
     "path": "a"
    }
   ]
 
 log-like templating
 
   $ hg annotate -T'{lines % "{rev} {node|shortest}: {line}"}' a
   0 8435: a
 
 '{lineno}' field should be populated as necessary
 
   $ hg annotate -T'{lines % "{rev}:{lineno}: {line}"}' a
   0:1: a
   $ hg annotate -Ta a \
   > --config templates.a='"{lines % "{rev}:{lineno}: {line}"}"'
   0:1: a
 
   $ cat <<EOF >>a
   > a
   > a
   > EOF
   $ hg ci -ma1 -d '1 0'
   $ hg cp a b
   $ hg ci -mb -d '1 0'
   $ cat <<EOF >> b
   > b4
   > b5
   > b6
   > EOF
   $ hg ci -mb2 -d '2 0'
 
 default output of '{lines}' should be readable
 
   $ hg annotate -T'{lines}' a
   0: a
   1: a
   1: a
   $ hg annotate -T'{join(lines, "\n")}' a
   0: a
   
   1: a
   
   1: a
 
 several filters can be applied to '{lines}'
 
   $ hg annotate -T'{lines|json}\n' a
   [{"line": "a\n", "rev": 0}, {"line": "a\n", "rev": 1}, {"line": "a\n", "rev": 1}]
   $ hg annotate -T'{lines|stringify}' a
   0: a
   1: a
   1: a
   $ hg annotate -T'{lines|count}\n' a
   3
 
 annotate multiple files (JSON)
 
   $ hg annotate -Tjson a b
   [
    {
     "lines": [{"line": "a\n", "rev": 0}, {"line": "a\n", "rev": 1}, {"line": "a\n", "rev": 1}],
     "path": "a"
    },
    {
     "lines": [{"line": "a\n", "rev": 0}, {"line": "a\n", "rev": 1}, {"line": "a\n", "rev": 1}, {"line": "b4\n", "rev": 3}, {"line": "b5\n", "rev": 3}, {"line": "b6\n", "rev": 3}],
     "path": "b"
    }
   ]
 
 annotate multiple files (template)
 
   $ hg annotate -T'== {path} ==\n{lines % "{rev}: {line}"}' a b
   == a ==
   0: a
   1: a
   1: a
   == b ==
   0: a
   1: a
   1: a
   3: b4
   3: b5
   3: b6
 
 annotate -n b
 
   $ hg annotate -n b
   0: a
   1: a
   1: a
   3: b4
   3: b5
   3: b6
 
 annotate --no-follow b
 
   $ hg annotate --no-follow b
   2: a
   2: a
   2: a
   3: b4
   3: b5
   3: b6
 
 annotate -nl b
 
   $ hg annotate -nl b
   0:1: a
   1:2: a
   1:3: a
   3:4: b4
   3:5: b5
   3:6: b6
 
 annotate -nf b
 
   $ hg annotate -nf b
   0 a: a
   1 a: a
   1 a: a
   3 b: b4
   3 b: b5
   3 b: b6
 
 annotate -nlf b
 
   $ hg annotate -nlf b
   0 a:1: a
   1 a:2: a
   1 a:3: a
   3 b:4: b4
   3 b:5: b5
   3 b:6: b6
 
   $ hg up -C 2
   1 files updated, 0 files merged, 0 files removed, 0 files unresolved
   $ cat <<EOF >> b
   > b4
   > c
   > b5
   > EOF
   $ hg ci -mb2.1 -d '2 0'
   created new head
   $ hg merge
   merging b
   warning: conflicts while merging b! (edit, then use 'hg resolve --mark')
   0 files updated, 0 files merged, 0 files removed, 1 files unresolved
   use 'hg resolve' to retry unresolved file merges or 'hg merge --abort' to abandon
   [1]
   $ cat b
   a
   a
   a
   <<<<<<< working copy: 5fbdc1152d97 - test: b2.1
   b4
   c
   b5
   ||||||| base
   =======
   b4
   b5
   b6
   >>>>>>> merge rev:    37ec9f5c3d1f - test: b2
   $ cat <<EOF > b
   > a
   > a
   > a
   > b4
   > c
   > b5
   > EOF
   $ hg resolve --mark -q
   $ rm b.orig
   $ hg ci -mmergeb -d '3 0'
 
 annotate after merge
 
   $ hg annotate -nf b
   0 a: a
   1 a: a
   1 a: a
   3 b: b4
   4 b: c
   3 b: b5
 
 annotate after merge with -l
 
   $ hg annotate -nlf b
   0 a:1: a
   1 a:2: a
   1 a:3: a
   3 b:4: b4
   4 b:5: c
   3 b:5: b5
 
   $ hg up -C 1
   0 files updated, 0 files merged, 1 files removed, 0 files unresolved
   $ hg cp a b
   $ cat <<EOF > b
   > a
   > z
   > a
   > EOF
   $ hg ci -mc -d '3 0'
   created new head
 Work around the pure version not resolving the conflict like native code
 #if pure
   $ hg merge
   merging b
   warning: conflicts while merging b! (edit, then use 'hg resolve --mark')
   0 files updated, 0 files merged, 0 files removed, 1 files unresolved
   use 'hg resolve' to retry unresolved file merges or 'hg merge --abort' to abandon
   [1]
   $ cat <<EOF > b
   > a
   > z
   > a
   > b4
   > c
   > b5
   > EOF
   $ hg resolve -m b
   (no more unresolved files)
   $ rm b.orig
 #else
   $ hg merge
   merging b
   0 files updated, 1 files merged, 0 files removed, 0 files unresolved
   (branch merge, don't forget to commit)
 #endif
   $ echo d >> b
   $ hg ci -mmerge2 -d '4 0'
 
 annotate after rename merge
 
   $ hg annotate -nf b
   0 a: a
   6 b: z
   1 a: a
   3 b: b4
   4 b: c
   3 b: b5
   7 b: d
 
 annotate after rename merge with -l
 
   $ hg annotate -nlf b
   0 a:1: a
   6 b:2: z
   1 a:3: a
   3 b:4: b4
   4 b:5: c
   3 b:5: b5
   7 b:7: d
 
 --skip nothing (should be the same as no --skip at all)
 
   $ hg annotate -nlf b --skip '1::0'
   0 a:1: a
   6 b:2: z
   1 a:3: a
   3 b:4: b4
   4 b:5: c
   3 b:5: b5
   7 b:7: d
 
 --skip a modified line. Note a slight behavior difference in pure - this is
 because the pure code comes up with slightly different deltas internally.
 
   $ hg annotate -nlf b --skip 6
   0 a:1: a
   1 a:2* z (no-pure !)
   0 a:1* z (pure !)
   1 a:3: a
   3 b:4: b4
   4 b:5: c
   3 b:5: b5
   7 b:7: d
 
 --skip added lines (and test multiple skip)
 
   $ hg annotate -nlf b --skip 3
   0 a:1: a
   6 b:2: z
   1 a:3: a
   1 a:3* b4
   4 b:5: c
   1 a:3* b5
   7 b:7: d
 
   $ hg annotate -nlf b --skip 4
   0 a:1: a
   6 b:2: z
   1 a:3: a
   3 b:4: b4
   1 a:3* c
   3 b:5: b5
   7 b:7: d
 
   $ hg annotate -nlf b --skip 3 --skip 4
   0 a:1: a
   6 b:2: z
   1 a:3: a
   1 a:3* b4
   1 a:3* c
   1 a:3* b5
   7 b:7: d
 
   $ hg annotate -nlf b --skip 'merge()'
   0 a:1: a
   6 b:2: z
   1 a:3: a
   3 b:4: b4
   4 b:5: c
   3 b:5: b5
   3 b:5* d
 
 --skip everything -- use the revision the file was introduced in
 
   $ hg annotate -nlf b --skip 'all()'
   0 a:1: a
   0 a:1* z
   0 a:1* a
   0 a:1* b4
   0 a:1* c
   0 a:1* b5
   0 a:1* d
 
 Issue2807: alignment of line numbers with -l
 
   $ echo more >> b
   $ hg ci -mmore -d '5 0'
   $ echo more >> b
   $ hg ci -mmore -d '6 0'
   $ echo more >> b
   $ hg ci -mmore -d '7 0'
   $ hg annotate -nlf b
    0 a: 1: a
    6 b: 2: z
    1 a: 3: a
    3 b: 4: b4
    4 b: 5: c
    3 b: 5: b5
    7 b: 7: d
    8 b: 8: more
    9 b: 9: more
   10 b:10: more
 
 linkrev vs rev
 
   $ hg annotate -r tip -n a
   0: a
   1: a
   1: a
 
 linkrev vs rev with -l
 
   $ hg annotate -r tip -nl a
   0:1: a
   1:2: a
   1:3: a
 
 Issue589: "undelete" sequence leads to crash
 
 annotate was crashing when trying to --follow something
 
 like A -> B -> A
 
 generate ABA rename configuration
 
   $ echo foo > foo
   $ hg add foo
   $ hg ci -m addfoo
   $ hg rename foo bar
   $ hg ci -m renamefoo
   $ hg rename bar foo
   $ hg ci -m renamebar
 
 annotate after ABA with follow
 
   $ hg annotate --follow foo
   foo: foo
 
 missing file
 
   $ hg ann nosuchfile
   abort: nosuchfile: no such file in rev e9e6b4fa872f
   [10]
 
 annotate file without '\n' on last line
 
   $ printf "" > c
   $ hg ci -A -m test -u nobody -d '1 0'
   adding c
   $ hg annotate c
   $ printf "a\nb" > c
   $ hg ci -m test
   $ hg annotate c
   [0-9]+: a (re)
   [0-9]+: b (re)
 
 Issue3841: check annotation of the file of which filelog includes
 merging between the revision and its ancestor
 
 to reproduce the situation with recent Mercurial, this script uses (1)
 "hg debugsetparents" to merge without ancestor check by "hg merge",
 and (2) the extension to allow filelog merging between the revision
 and its ancestor by overriding "repo._filecommit".
 
   $ cat > ../legacyrepo.py <<EOF
   > from __future__ import absolute_import
   > from mercurial import commit, error, extensions
   > def _filecommit(orig, repo, fctx, manifest1, manifest2,
   >                 linkrev, tr, includecopymeta, ms):
   >     fname = fctx.path()
   >     text = fctx.data()
   >     flog = repo.file(fname)
   >     fparent1 = manifest1.get(fname, repo.nullid)
   >     fparent2 = manifest2.get(fname, repo.nullid)
   >     meta = {}
   >     copy = fctx.copysource()
   >     if copy and copy != fname:
   >         raise error.Abort('copying is not supported')
   >     if fparent2 != repo.nullid:
   >         return flog.add(text, meta, tr, linkrev,
   >                         fparent1, fparent2), 'modified'
   >     raise error.Abort('only merging is supported')
   > def uisetup(ui):
   >     extensions.wrapfunction(commit, '_filecommit', _filecommit)
   > EOF
 
   $ cat > baz <<EOF
   > 1
   > 2
   > 3
   > 4
   > 5
   > EOF
   $ hg add baz
   $ hg commit -m "baz:0"
 
   $ cat > baz <<EOF
   > 1 baz:1
   > 2
   > 3
   > 4
   > 5
   > EOF
   $ hg commit -m "baz:1"
 
   $ cat > baz <<EOF
   > 1 baz:1
   > 2 baz:2
   > 3
   > 4
   > 5
   > EOF
   $ hg debugsetparents 17 17
   $ hg --config extensions.legacyrepo=../legacyrepo.py  commit -m "baz:2"
   $ hg debugindexdot baz
   digraph G {
   	-1 -> 0
   	0 -> 1
   	1 -> 2
   	1 -> 2
   }
   $ hg annotate baz
   17: 1 baz:1
   18: 2 baz:2
   16: 3
   16: 4
   16: 5
 
   $ cat > baz <<EOF
   > 1 baz:1
   > 2 baz:2
   > 3 baz:3
   > 4
   > 5
   > EOF
   $ hg commit -m "baz:3"
 
   $ cat > baz <<EOF
   > 1 baz:1
   > 2 baz:2
   > 3 baz:3
   > 4 baz:4
   > 5
   > EOF
   $ hg debugsetparents 19 18
   $ hg --config extensions.legacyrepo=../legacyrepo.py  commit -m "baz:4"
   $ hg debugindexdot baz
   digraph G {
   	-1 -> 0
   	0 -> 1
   	1 -> 2
   	1 -> 2
   	2 -> 3
   	3 -> 4
   	2 -> 4
   }
   $ hg annotate baz
   17: 1 baz:1
   18: 2 baz:2
   19: 3 baz:3
   20: 4 baz:4
   16: 5
 
 annotate clean file
 
   $ hg annotate -ncr "wdir()" foo
   11 472b18db256d : foo
 
 annotate modified file
 
   $ echo foofoo >> foo
   $ hg annotate -r "wdir()" foo
   11 : foo
   20+: foofoo
 
   $ hg annotate -cr "wdir()" foo
   472b18db256d : foo
   b6bedd5477e7+: foofoo
 
   $ hg annotate -ncr "wdir()" foo
   11 472b18db256d : foo
   20 b6bedd5477e7+: foofoo
 
   $ hg annotate --debug -ncr "wdir()" foo
   11 472b18db256d1e8282064eab4bfdaf48cbfe83cd : foo
   20 b6bedd5477e797f25e568a6402d4697f3f895a72+: foofoo
 
   $ hg annotate -udr "wdir()" foo
   test Thu Jan 01 00:00:00 1970 +0000: foo
   test [A-Za-z0-9:+ ]+: foofoo (re)
 
   $ hg annotate -ncr "wdir()" -Tjson foo
   [
    {
     "lines": [{"line": "foo\n", "node": "472b18db256d1e8282064eab4bfdaf48cbfe83cd", "rev": 11}, {"line": "foofoo\n", "node": "ffffffffffffffffffffffffffffffffffffffff", "rev": 2147483647}],
     "path": "foo"
    }
   ]
 
 annotate added file
 
   $ echo bar > bar
   $ hg add bar
   $ hg annotate -ncr "wdir()" bar
   20 b6bedd5477e7+: bar
 
 annotate renamed file
 
   $ hg rename foo renamefoo2
   $ hg annotate -ncr "wdir()" renamefoo2
   11 472b18db256d : foo
   20 b6bedd5477e7+: foofoo
 
 annotate missing file
 
   $ rm baz
 
   $ hg annotate -ncr "wdir()" baz
   abort: $TESTTMP\repo/baz: $ENOENT$ (windows !)
   abort: $ENOENT$: '$TESTTMP/repo/baz' (no-windows !)
   [255]
 
 annotate removed file
 
   $ hg rm baz
 
   $ hg annotate -ncr "wdir()" baz
   abort: $TESTTMP\repo/baz: $ENOENT$ (windows !)
   abort: $ENOENT$: '$TESTTMP/repo/baz' (no-windows !)
   [255]
 
   $ hg revert --all --no-backup --quiet
   $ hg id -n
   20
 
 Test followlines() revset; we usually check both followlines(pat, range) and
 followlines(pat, range, descend=True) to make sure both give the same result
 when they should.
 
   $ echo a >> foo
   $ hg ci -m 'foo: add a'
   $ hg log -T '{rev}: {desc}\n' -r 'followlines(baz, 3:5)'
   16: baz:0
   19: baz:3
   20: baz:4
   $ hg log -T '{rev}: {desc}\n' -r 'followlines(baz, 3:5, startrev=20)'
   16: baz:0
   19: baz:3
   20: baz:4
   $ hg log -T '{rev}: {desc}\n' -r 'followlines(baz, 3:5, startrev=19)'
   16: baz:0
   19: baz:3
   $ hg log -T '{rev}: {desc}\n' -r 'followlines(baz, 3:5, startrev=19, descend=True)'
   19: baz:3
   20: baz:4
   $ printf "0\n0\n" | cat - baz > baz1
   $ mv baz1 baz
   $ hg ci -m 'added two lines with 0'
   $ hg log -T '{rev}: {desc}\n' -r 'followlines(baz, 5:7)'
   16: baz:0
   19: baz:3
   20: baz:4
   $ hg log -T '{rev}: {desc}\n' -r 'followlines(baz, 3:5, descend=true, startrev=19)'
   19: baz:3
   20: baz:4
   $ echo 6 >> baz
   $ hg ci -m 'added line 8'
   $ hg log -T '{rev}: {desc}\n' -r 'followlines(baz, 5:7)'
   16: baz:0
   19: baz:3
   20: baz:4
   $ hg log -T '{rev}: {desc}\n' -r 'followlines(baz, 3:5, startrev=19, descend=1)'
   19: baz:3
   20: baz:4
   $ sed 's/3/3+/' baz > baz.new
   $ mv baz.new baz
   $ hg ci -m 'baz:3->3+'
   $ hg log -T '{rev}: {desc}\n' -r 'followlines(baz, 5:7, descend=0)'
   16: baz:0
   19: baz:3
   20: baz:4
   24: baz:3->3+
   $ hg log -T '{rev}: {desc}\n' -r 'followlines(baz, 3:5, startrev=17, descend=True)'
   19: baz:3
   20: baz:4
   24: baz:3->3+
   $ hg log -T '{rev}: {desc}\n' -r 'followlines(baz, 1:2, descend=false)'
   22: added two lines with 0
 
 file patterns are okay
   $ hg log -T '{rev}: {desc}\n' -r 'followlines("path:baz", 1:2)'
   22: added two lines with 0
 
 renames are followed
   $ hg mv baz qux
   $ sed 's/4/4+/' qux > qux.new
   $ mv qux.new qux
   $ hg ci -m 'qux:4->4+'
   $ hg log -T '{rev}: {desc}\n' -r 'followlines(qux, 5:7)'
   16: baz:0
   19: baz:3
   20: baz:4
   24: baz:3->3+
   25: qux:4->4+
 
 but are missed when following children
   $ hg log -T '{rev}: {desc}\n' -r 'followlines(baz, 5:7, startrev=22, descend=True)'
   24: baz:3->3+
 
 merge
   $ hg up 24 --quiet
   $ echo 7 >> baz
   $ hg ci -m 'one more line, out of line range'
   created new head
   $ sed 's/3+/3-/' baz > baz.new
   $ mv baz.new baz
   $ hg ci -m 'baz:3+->3-'
   $ hg log -T '{rev}: {desc}\n' -r 'followlines(baz, 5:7)'
   16: baz:0
   19: baz:3
   20: baz:4
   24: baz:3->3+
   27: baz:3+->3-
   $ hg merge 25
   merging baz and qux to qux
   warning: conflicts while merging qux! (edit, then use 'hg resolve --mark')
   0 files updated, 0 files merged, 0 files removed, 1 files unresolved
   use 'hg resolve' to retry unresolved file merges or 'hg merge --abort' to abandon
   [1]
   $ cat qux
   0
   0
   1 baz:1
   2 baz:2
   <<<<<<< working copy: 863de62655ef - test: baz:3+->3-
   3- baz:3
   4 baz:4
   ||||||| base
   3+ baz:3
   4 baz:4
   =======
   3+ baz:3
   4+ baz:4
   >>>>>>> merge rev:    cb8df70ae185 - test: qux:4->4+
   5
   6
   7
   $ cat > qux <<EOF
   > 0
   > 0
   > 1 baz:1
   > 2 baz:2
   > 3- baz:3
   > 4 baz:4
   > 5
   > 6
   > 7
   > EOF
   $ hg resolve --mark -q
   $ rm qux.orig
   $ hg ci -m merge
   $ hg log -T '{rev}: {desc}\n' -r 'followlines(qux, 5:7)'
   16: baz:0
   19: baz:3
   20: baz:4
   24: baz:3->3+
   25: qux:4->4+
   27: baz:3+->3-
   28: merge
   $ hg up 25 --quiet
   $ hg merge 27
   merging qux and baz to qux
   warning: conflicts while merging qux! (edit, then use 'hg resolve --mark')
   0 files updated, 0 files merged, 0 files removed, 1 files unresolved
   use 'hg resolve' to retry unresolved file merges or 'hg merge --abort' to abandon
   [1]
   $ cat qux
   0
   0
   1 baz:1
   2 baz:2
   <<<<<<< working copy: cb8df70ae185 - test: qux:4->4+
   3+ baz:3
   4+ baz:4
   ||||||| base
   3+ baz:3
   4 baz:4
   =======
   3- baz:3
   4 baz:4
   >>>>>>> merge rev:    863de62655ef - test: baz:3+->3-
   5
   6
   7
   $ cat > qux <<EOF
   > 0
   > 0
   > 1 baz:1
   > 2 baz:2
   > 3+ baz:3
   > 4+ baz:4
   > 5
   > 6
   > EOF
   $ hg resolve --mark -q
   $ rm qux.orig
   $ hg ci -m 'merge from other side'
   created new head
   $ hg log -T '{rev}: {desc}\n' -r 'followlines(qux, 5:7)'
   16: baz:0
   19: baz:3
   20: baz:4
   24: baz:3->3+
   25: qux:4->4+
   27: baz:3+->3-
   29: merge from other side
   $ hg up 24 --quiet
 
 we are missing the branch with rename when following children
   $ hg log -T '{rev}: {desc}\n' -r 'followlines(baz, 5:7, startrev=26, descend=True)'
   27: baz:3+->3-
 
 we follow all branches in descending direction
   $ hg up 23 --quiet
   $ sed 's/3/+3/' baz > baz.new
   $ mv baz.new baz
   $ hg ci -m 'baz:3->+3'
   created new head
   $ hg log -T '{rev}: {desc}\n' -r 'followlines(baz, 2:5, startrev=16, descend=True)' --graph
   @  30: baz:3->+3
   :
   : o  27: baz:3+->3-
   : :
   : o  24: baz:3->3+
   :/
   o    20: baz:4
   |\
   | o  19: baz:3
   |/
   o  18: baz:2
   :
   o  16: baz:0
   |
   ~
 
 Issue5595: on a merge changeset with different line ranges depending on
 parent, be conservative and use the surrounding interval to avoid loosing
 track of possible further descendants in specified range.
 
   $ hg up 23 --quiet
   $ hg cat baz -r 24
   0
   0
   1 baz:1
   2 baz:2
   3+ baz:3
   4 baz:4
   5
   6
   $ cat > baz << EOF
   > 0
   > 0
   > a
   > b
   > 3+ baz:3
   > 4 baz:4
   > y
   > z
   > EOF
   $ hg ci -m 'baz: mostly rewrite with some content from 24'
   created new head
   $ hg merge --tool :merge-other 24
   merging baz
-  1 files updated, 0 files merged, 0 files removed, 0 files unresolved
+  0 files updated, 1 files merged, 0 files removed, 0 files unresolved
   (branch merge, don't forget to commit)
   $ hg ci -m 'merge forgetting about baz rewrite'
   $ cat > baz << EOF
   > 0
   > 0
   > 1 baz:1
   > 2+ baz:2
   > 3+ baz:3
   > 4 baz:4
   > 5
   > 6
   > EOF
   $ hg ci -m 'baz: narrow change (2->2+)'
   $ hg log -T '{rev}: {desc}\n' -r 'followlines(baz, 3:4, startrev=20, descend=True)' --graph
   @  33: baz: narrow change (2->2+)
   |
   o    32: merge forgetting about baz rewrite
   |\
   | o  31: baz: mostly rewrite with some content from 24
   | :
   | : o  30: baz:3->+3
   | :/
   +---o  27: baz:3+->3-
   | :
   o :  24: baz:3->3+
   :/
   o    20: baz:4
   |\
   ~ ~
 
 An integer as a line range, which is parsed as '1:1'
 
   $ hg log -r 'followlines(baz, 1)'
   changeset:   22:2174d0bf352a
   user:        test
   date:        Thu Jan 01 00:00:00 1970 +0000
   summary:     added two lines with 0
   
 
 check error cases
   $ hg up 24 --quiet
   $ hg log -r 'followlines()'
   hg: parse error: followlines takes at least 1 positional arguments
   [10]
   $ hg log -r 'followlines(baz)'
   hg: parse error: followlines requires a line range
   [10]
   $ hg log -r 'followlines(baz, x)'
   hg: parse error: followlines expects a line number or a range
   [10]
   $ hg log -r 'followlines(baz, 1:2, startrev=desc("b"))'
   hg: parse error: followlines expects exactly one revision
   [10]
   $ hg log -r 'followlines("glob:*", 1:2)'
   hg: parse error: followlines expects exactly one file
   [10]
   $ hg log -r 'followlines(baz, 1:)'
   hg: parse error: line range bounds must be integers
   [10]
   $ hg log -r 'followlines(baz, :1)'
   hg: parse error: line range bounds must be integers
   [10]
   $ hg log -r 'followlines(baz, x:4)'
   hg: parse error: line range bounds must be integers
   [10]
   $ hg log -r 'followlines(baz, 5:4)'
   hg: parse error: line range must be positive
   [10]
   $ hg log -r 'followlines(baz, 0:4)'
   hg: parse error: fromline must be strictly positive
   [10]
   $ hg log -r 'followlines(baz, 2:40)'
   abort: line range exceeds file size
   [10]
   $ hg log -r 'followlines(baz, 2:4, startrev=20, descend=[1])'
   hg: parse error at 43: not a prefix: [
   (followlines(baz, 2:4, startrev=20, descend=[1])
                                               ^ here)
   [10]
   $ hg log -r 'followlines(baz, 2:4, startrev=20, descend=a)'
   hg: parse error: descend argument must be a boolean
   [10]
 
 Test empty annotate output
 
   $ printf '\0' > binary
   $ touch empty
   $ hg ci -qAm 'add binary and empty files'
 
   $ hg annotate binary empty
   binary: binary file
 
   $ hg annotate -Tjson binary empty
   [
    {
     "path": "binary"
    },
    {
     "lines": [],
     "path": "empty"
    }
   ]
 
 Test annotate with whitespace options
 
   $ cd ..
   $ hg init repo-ws
   $ cd repo-ws
   $ cat > a <<EOF
   > aa
   > 
   > b b
   > EOF
   $ hg ci -Am "adda"
   adding a
   $ sed 's/EOL$//g' > a <<EOF
   > a  a
   > 
   >  EOL
   > b  b
   > EOF
   $ hg ci -m "changea"
 
 Annotate with no option
 
   $ hg annotate a
   1: a  a
   0: 
   1:  
   1: b  b
 
 Annotate with --ignore-space-change
 
   $ hg annotate --ignore-space-change a
   1: a  a
   1: 
   0:  
   0: b  b
 
 Annotate with --ignore-all-space
 
   $ hg annotate --ignore-all-space a
   0: a  a
   0: 
   1:  
   0: b  b
 
 Annotate with --ignore-blank-lines (similar to no options case)
 
   $ hg annotate --ignore-blank-lines a
   1: a  a
   0: 
   1:  
   1: b  b
 
   $ cd ..
 
 Annotate with orphaned CR (issue5798)
 -------------------------------------
 
   $ hg init repo-cr
   $ cd repo-cr
 
   $ cat <<'EOF' >> "$TESTTMP/substcr.py"
   > import sys
   > from mercurial.utils import procutil
   > procutil.setbinary(sys.stdin)
   > procutil.setbinary(sys.stdout)
   > stdin = getattr(sys.stdin, 'buffer', sys.stdin)
   > stdout = getattr(sys.stdout, 'buffer', sys.stdout)
   > stdout.write(stdin.read().replace(b'\r', b'[CR]'))
   > EOF
 
   >>> with open('a', 'wb') as f:
   ...     f.write(b'0a\r0b\r\n0c\r0d\r\n0e\n0f\n0g') and None
   $ hg ci -qAm0
   >>> with open('a', 'wb') as f:
   ...     f.write(b'0a\r0b\r\n1c\r1d\r\n0e\n1f\n0g') and None
   $ hg ci -m1
 
   $ hg annotate -r0 a | "$PYTHON" "$TESTTMP/substcr.py"
   0: 0a[CR]0b[CR]
   0: 0c[CR]0d[CR]
   0: 0e
   0: 0f
   0: 0g
   $ hg annotate -r1 a | "$PYTHON" "$TESTTMP/substcr.py"
   0: 0a[CR]0b[CR]
   1: 1c[CR]1d[CR]
   0: 0e
   1: 1f
   0: 0g
 
   $ cd ..
 
 Annotate with linkrev pointing to another branch
 ------------------------------------------------
 
 create history with a filerev whose linkrev points to another branch
 
   $ hg init branchedlinkrev
   $ cd branchedlinkrev
   $ echo A > a
   $ hg commit -Am 'contentA'
   adding a
   $ echo B >> a
   $ hg commit -m 'contentB'
   $ hg up --rev 'desc(contentA)'
   1 files updated, 0 files merged, 0 files removed, 0 files unresolved
   $ echo unrelated > unrelated
   $ hg commit -Am 'unrelated'
   adding unrelated
   created new head
   $ hg graft -r 'desc(contentB)'
   grafting 1:fd27c222e3e6 "contentB"
   $ echo C >> a
   $ hg commit -m 'contentC'
   $ echo W >> a
   $ hg log -G
   @  changeset:   4:072f1e8df249
   |  tag:         tip
   |  user:        test
   |  date:        Thu Jan 01 00:00:00 1970 +0000
   |  summary:     contentC
   |
   o  changeset:   3:ff38df03cc4b
   |  user:        test
   |  date:        Thu Jan 01 00:00:00 1970 +0000
   |  summary:     contentB
   |
   o  changeset:   2:62aaf3f6fc06
   |  parent:      0:f0932f74827e
   |  user:        test
   |  date:        Thu Jan 01 00:00:00 1970 +0000
   |  summary:     unrelated
   |
   | o  changeset:   1:fd27c222e3e6
   |/   user:        test
   |    date:        Thu Jan 01 00:00:00 1970 +0000
   |    summary:     contentB
   |
   o  changeset:   0:f0932f74827e
      user:        test
      date:        Thu Jan 01 00:00:00 1970 +0000
      summary:     contentA
   
 
 Annotate should list ancestor of starting revision only
 
   $ hg annotate a
   0: A
   3: B
   4: C
 
   $ hg annotate a -r 'wdir()'
   0 : A
   3 : B
   4 : C
   4+: W
 
 Even when the starting revision is the linkrev-shadowed one:
 
   $ hg annotate a -r 3
   0: A
   3: B
 
   $ cd ..
 
 Issue5360: Deleted chunk in p1 of a merge changeset
 
   $ hg init repo-5360
   $ cd repo-5360
   $ echo 1 > a
   $ hg commit -A a -m 1
   $ echo 2 >> a
   $ hg commit -m 2
   $ echo a > a
   $ hg commit -m a
   $ hg update '.^' -q
   $ echo 3 >> a
   $ hg commit -m 3 -q
   $ hg merge 2 -q
   warning: conflicts while merging a! (edit, then use 'hg resolve --mark')
   [1]
   $ cat a
   <<<<<<< working copy: 0a068f0261cf - test: 3
   1
   2
   3
   ||||||| base
   1
   2
   =======
   a
   >>>>>>> merge rev:    9409851bc20a - test: a
   $ cat > a << EOF
   > b
   > 1
   > 2
   > 3
   > a
   > EOF
   $ hg resolve --mark -q
   $ rm a.orig
   $ hg commit -m m
   $ hg annotate a
   4: b
   0: 1
   1: 2
   3: 3
   2: a
 
   $ cd ..

tests/test-conflict.t

@@ -1,422 +1,422 b''
   $ hg init
   $ cat << EOF > a
   > Small Mathematical Series.
   > One
   > Two
   > Three
   > Four
   > Five
   > Hop we are done.
   > EOF
   $ hg add a
   $ hg commit -m ancestor
   $ cat << EOF > a
   > Small Mathematical Series.
   > 1
   > 2
   > 3
   > 4
   > 5
   > Hop we are done.
   > EOF
   $ hg commit -m branch1
   $ hg co 0
   1 files updated, 0 files merged, 0 files removed, 0 files unresolved
   $ cat << EOF > a
   > Small Mathematical Series.
   > 1
   > 2
   > 3
   > 6
   > 8
   > Hop we are done.
   > EOF
   $ hg commit -m branch2
   created new head
 
   $ hg merge 1
   merging a
   warning: conflicts while merging a! (edit, then use 'hg resolve --mark')
   0 files updated, 0 files merged, 0 files removed, 1 files unresolved
   use 'hg resolve' to retry unresolved file merges or 'hg merge --abort' to abandon
   [1]
 
   $ hg id
   618808747361+c0c68e4fe667+ tip
 
   $ echo "[commands]" >> $HGRCPATH
   $ echo "status.verbose=true" >> $HGRCPATH
   $ hg status
   M a
   ? a.orig
   # The repository is in an unfinished *merge* state.
   
   # Unresolved merge conflicts:
   # 
   #     a
   # 
   # To mark files as resolved:  hg resolve --mark FILE
   
   # To continue:    hg commit
   # To abort:       hg merge --abort
   
   $ hg status -Tjson
   [
    {
     "itemtype": "file",
     "path": "a",
     "status": "M",
     "unresolved": true
    },
    {
     "itemtype": "file",
     "path": "a.orig",
     "status": "?"
    },
    {
     "itemtype": "morestatus",
     "unfinished": "merge",
     "unfinishedmsg": "To continue:    hg commit\nTo abort:       hg merge --abort"
    }
   ]
 
   $ hg status -0
   M a\x00? a.orig\x00 (no-eol) (esc)
   $ cat a
   Small Mathematical Series.
   1
   2
   3
   <<<<<<< working copy: 618808747361 - test: branch2
   6
   8
   =======
   4
   5
   >>>>>>> merge rev:    c0c68e4fe667 - test: branch1
   Hop we are done.
 
   $ hg status --config commands.status.verbose=0
   M a
   ? a.orig
 
 Verify custom conflict markers
 
   $ hg up -q --clean .
   $ cat <<EOF >> .hg/hgrc
   > [command-templates]
   > mergemarker = '{author} {rev}'
   > EOF
 
   $ hg merge 1
   merging a
   warning: conflicts while merging a! (edit, then use 'hg resolve --mark')
   0 files updated, 0 files merged, 0 files removed, 1 files unresolved
   use 'hg resolve' to retry unresolved file merges or 'hg merge --abort' to abandon
   [1]
 
   $ cat a
   Small Mathematical Series.
   1
   2
   3
   <<<<<<< working copy: test 2
   6
   8
   =======
   4
   5
   >>>>>>> merge rev:    test 1
   Hop we are done.
 
 Verify custom conflict markers with legacy config name
 
   $ hg up -q --clean .
   $ cat <<EOF >> .hg/hgrc
   > [ui]
   > mergemarkertemplate = '{author} {rev}'
   > EOF
 
   $ hg merge 1
   merging a
   warning: conflicts while merging a! (edit, then use 'hg resolve --mark')
   0 files updated, 0 files merged, 0 files removed, 1 files unresolved
   use 'hg resolve' to retry unresolved file merges or 'hg merge --abort' to abandon
   [1]
 
   $ cat a
   Small Mathematical Series.
   1
   2
   3
   <<<<<<< working copy: test 2
   6
   8
   =======
   4
   5
   >>>>>>> merge rev:    test 1
   Hop we are done.
 
 Verify line splitting of custom conflict marker which causes multiple lines
 
   $ hg up -q --clean .
   $ cat >> .hg/hgrc <<EOF
   > [command-templates]
   > mergemarker={author} {rev}\nfoo\nbar\nbaz
   > EOF
 
   $ hg -q merge 1
   warning: conflicts while merging a! (edit, then use 'hg resolve --mark')
   [1]
 
   $ cat a
   Small Mathematical Series.
   1
   2
   3
   <<<<<<< working copy: test 2
   6
   8
   =======
   4
   5
   >>>>>>> merge rev:    test 1
   Hop we are done.
 
 Verify line trimming of custom conflict marker using multi-byte characters
 
   $ hg up -q --clean .
   $ "$PYTHON" <<EOF
   > fp = open('logfile', 'wb')
   > fp.write(b'12345678901234567890123456789012345678901234567890' +
   >          b'1234567890') # there are 5 more columns for 80 columns
   > 
   > # 2 x 4 = 8 columns, but 3 x 4 = 12 bytes
   > fp.write(u'\u3042\u3044\u3046\u3048'.encode('utf-8'))
   > 
   > fp.close()
   > EOF
   $ hg add logfile
   $ hg --encoding utf-8 commit --logfile logfile
 
   $ cat >> .hg/hgrc <<EOF
   > [command-templates]
   > mergemarker={desc|firstline}
   > EOF
 
   $ hg -q --encoding utf-8 merge 1
   warning: conflicts while merging a! (edit, then use 'hg resolve --mark')
   [1]
 
   $ cat a
   Small Mathematical Series.
   1
   2
   3
   <<<<<<< working copy: 1234567890123456789012345678901234567890123456789012345...
   6
   8
   =======
   4
   5
   >>>>>>> merge rev:    branch1
   Hop we are done.
 
 Verify basic conflict markers
 
   $ hg up -q --clean 2
   $ printf "\n[ui]\nmergemarkers=basic\n" >> .hg/hgrc
 
   $ hg merge 1
   merging a
   warning: conflicts while merging a! (edit, then use 'hg resolve --mark')
   0 files updated, 0 files merged, 0 files removed, 1 files unresolved
   use 'hg resolve' to retry unresolved file merges or 'hg merge --abort' to abandon
   [1]
 
   $ cat a
   Small Mathematical Series.
   1
   2
   3
   <<<<<<< working copy
   6
   8
   =======
   4
   5
   >>>>>>> merge rev
   Hop we are done.
 
 internal:merge3
 
   $ hg up -q --clean .
 
   $ hg merge 1 --tool internal:merge3
   merging a
   warning: conflicts while merging a! (edit, then use 'hg resolve --mark')
   0 files updated, 0 files merged, 0 files removed, 1 files unresolved
   use 'hg resolve' to retry unresolved file merges or 'hg merge --abort' to abandon
   [1]
   $ cat a
   Small Mathematical Series.
   <<<<<<< working copy
   1
   2
   3
   6
   8
   ||||||| base
   One
   Two
   Three
   Four
   Five
   =======
   1
   2
   3
   4
   5
   >>>>>>> merge rev
   Hop we are done.
 
 internal:mergediff
 
   $ hg co -C 1
   1 files updated, 0 files merged, 0 files removed, 0 files unresolved
   $ cat << EOF > a
   > Small Mathematical Series.
   > 1
   > 2
   > 3
   > 4
   > 4.5
   > 5
   > Hop we are done.
   > EOF
   $ hg co -m 2 -t internal:mergediff
   merging a
   warning: conflicts while merging a! (edit, then use 'hg resolve --mark')
   0 files updated, 0 files merged, 0 files removed, 1 files unresolved
   use 'hg resolve' to retry unresolved file merges
   [1]
   $ cat a
   Small Mathematical Series.
   1
   2
   3
   <<<<<<<
   ------- base
   +++++++ working copy
    4
   +4.5
    5
   ======= destination
   6
   8
   >>>>>>>
   Hop we are done.
 Test the same thing as above but modify a bit more so we instead get the working
 copy in full and the diff from base to destination.
   $ hg co -C 1
   1 files updated, 0 files merged, 0 files removed, 0 files unresolved
   $ cat << EOF > a
   > Small Mathematical Series.
   > 1
   > 2
   > 3.5
   > 4.5
   > 5.5
   > Hop we are done.
   > EOF
   $ hg co -m 2 -t internal:mergediff
   merging a
   warning: conflicts while merging a! (edit, then use 'hg resolve --mark')
   0 files updated, 0 files merged, 0 files removed, 1 files unresolved
   use 'hg resolve' to retry unresolved file merges
   [1]
   $ cat a
   Small Mathematical Series.
   1
   2
   <<<<<<<
   ======= working copy
   3.5
   4.5
   5.5
   ------- base
   +++++++ destination
    3
   -4
   -5
   +6
   +8
   >>>>>>>
   Hop we are done.
 
 Add some unconflicting changes on each head, to make sure we really
 are merging, unlike :local and :other
 
   $ hg up -C
   2 files updated, 0 files merged, 0 files removed, 0 files unresolved
   updated to "e0693e20f496: 123456789012345678901234567890123456789012345678901234567890????"
   1 other heads for branch "default"
   $ printf "\n\nEnd of file\n" >> a
   $ hg ci -m "Add some stuff at the end"
   $ hg up -r 1
   1 files updated, 0 files merged, 1 files removed, 0 files unresolved
   $ printf "Start of file\n\n\n" > tmp
   $ cat a >> tmp
   $ mv tmp a
   $ hg ci -m "Add some stuff at the beginning"
 
 Now test :merge-other and :merge-local
 
   $ hg merge
   merging a
   warning: conflicts while merging a! (edit, then use 'hg resolve --mark')
   1 files updated, 0 files merged, 0 files removed, 1 files unresolved
   use 'hg resolve' to retry unresolved file merges or 'hg merge --abort' to abandon
   [1]
   $ hg resolve --tool :merge-other a
   merging a
   (no more unresolved files)
   $ cat a
   Start of file
   
   
   Small Mathematical Series.
   1
   2
   3
   6
   8
   Hop we are done.
   
   
   End of file
 
   $ hg up -C
   1 files updated, 0 files merged, 1 files removed, 0 files unresolved
   updated to "18b51d585961: Add some stuff at the beginning"
   1 other heads for branch "default"
   $ hg merge --tool :merge-local
   merging a
-  2 files updated, 0 files merged, 0 files removed, 0 files unresolved
+  1 files updated, 1 files merged, 0 files removed, 0 files unresolved
   (branch merge, don't forget to commit)
   $ cat a
   Start of file
   
   
   Small Mathematical Series.
   1
   2
   3
   4
   5
   Hop we are done.
   
   
   End of file

tests/test-copies-chain-merge.t

@@ -1,3850 +1,3850 b''
 #testcases filelog compatibility changeset sidedata upgraded upgraded-parallel pull push pull-upgrade push-upgrade
 
 =====================================================
 Test Copy tracing for chain of copies involving merge
 =====================================================
 
 This test files covers copies/rename case for a chains of commit where merges
 are involved. It cheks we do not have unwanted update of behavior and that the
 different options to retrieve copies behave correctly.
 
 
 Setup
 =====
 
 use git diff to see rename
 
   $ cat << EOF >> ./no-linkrev
   > #!$PYTHON
   > # filter out linkrev part of the debugindex command
   > import sys
   > for line in sys.stdin:
   >     if " linkrev " in line:
   >         print(line.rstrip())
   >     else:
   >         l = "%s       *%s" % (line[:6], line[14:].rstrip())
   >         print(l)
   > EOF
 
   $ cat << EOF >> $HGRCPATH
   > [diff]
   > git=yes
   > [command-templates]
   > log={desc}\n
   > EOF
 
 #if compatibility
   $ cat >> $HGRCPATH << EOF
   > [experimental]
   > copies.read-from = compatibility
   > EOF
 #endif
 
 #if changeset
   $ cat >> $HGRCPATH << EOF
   > [experimental]
   > copies.read-from = changeset-only
   > copies.write-to = changeset-only
   > EOF
 #endif
 
 #if sidedata
   $ cat >> $HGRCPATH << EOF
   > [format]
   > exp-use-copies-side-data-changeset = yes
   > EOF
 #endif
 
 #if pull
   $ cat >> $HGRCPATH << EOF
   > [format]
   > exp-use-copies-side-data-changeset = yes
   > EOF
 #endif
 
 #if push
   $ cat >> $HGRCPATH << EOF
   > [format]
   > exp-use-copies-side-data-changeset = yes
   > EOF
 #endif
 
 #if pull-upgrade
   $ cat >> $HGRCPATH << EOF
   > [format]
   > exp-use-copies-side-data-changeset = no
   > [experimental]
   > changegroup4 = yes
   > EOF
 #endif
 
 #if push-upgrade
   $ cat >> $HGRCPATH << EOF
   > [format]
   > exp-use-copies-side-data-changeset = no
   > [experimental]
   > changegroup4 = yes
   > EOF
 #endif
 
   $ cat > same-content.txt << EOF
   > Here is some content that will be the same accros multiple file.
   > 
   > This is done on purpose so that we end up in some merge situation, were the
   > resulting content is the same as in the parent(s), but a new filenodes still
   > need to be created to record some file history information (especially
   > about copies).
   > EOF
 
   $ hg init repo-chain
   $ cd repo-chain
 
 Add some linear rename initialy
 
   $ cp ../same-content.txt a
   $ cp ../same-content.txt b
   $ cp ../same-content.txt h
   $ echo "original content for P" > p
   $ echo "original content for Q" > q
   $ echo "original content for R" > r
   $ hg ci -Am 'i-0 initial commit: a b h p q r'
   adding a
   adding b
   adding h
   adding p
   adding q
   adding r
   $ hg mv a c
   $ hg mv p s
   $ hg ci -Am 'i-1: a -move-> c, p -move-> s'
   $ hg mv c d
   $ hg mv s t
   $ hg ci -Am 'i-2: c -move-> d, s -move-> t'
   $ hg log -G
   @  i-2: c -move-> d, s -move-> t
   |
   o  i-1: a -move-> c, p -move-> s
   |
   o  i-0 initial commit: a b h p q r
   
 
 And having another branch with renames on the other side
 
   $ hg mv d e
   $ hg ci -Am 'a-1: d -move-> e'
   $ hg mv e f
   $ hg ci -Am 'a-2: e -move-> f'
   $ hg log -G --rev '::.'
   @  a-2: e -move-> f
   |
   o  a-1: d -move-> e
   |
   o  i-2: c -move-> d, s -move-> t
   |
   o  i-1: a -move-> c, p -move-> s
   |
   o  i-0 initial commit: a b h p q r
   
 
 Have a branching with nothing on one side
 
   $ hg up 'desc("i-2")'
   1 files updated, 0 files merged, 1 files removed, 0 files unresolved
   $ echo foo > b
   $ hg ci -m 'b-1: b update'
   created new head
   $ hg log -G --rev '::.'
   @  b-1: b update
   |
   o  i-2: c -move-> d, s -move-> t
   |
   o  i-1: a -move-> c, p -move-> s
   |
   o  i-0 initial commit: a b h p q r
   
 
 Create a branch that delete a file previous renamed
 
   $ hg up 'desc("i-2")'
   1 files updated, 0 files merged, 0 files removed, 0 files unresolved
   $ hg rm d
   $ hg ci -m 'c-1 delete d'
   created new head
   $ hg log -G --rev '::.'
   @  c-1 delete d
   |
   o  i-2: c -move-> d, s -move-> t
   |
   o  i-1: a -move-> c, p -move-> s
   |
   o  i-0 initial commit: a b h p q r
   
 
 Create a branch that delete a file previous renamed and recreate it
 
   $ hg up 'desc("i-2")'
   1 files updated, 0 files merged, 0 files removed, 0 files unresolved
   $ hg rm d
   $ hg ci -m 'd-1 delete d'
   created new head
   $ echo bar > d
   $ hg add d
   $ hg ci -m 'd-2 re-add d'
   $ hg log -G --rev '::.'
   @  d-2 re-add d
   |
   o  d-1 delete d
   |
   o  i-2: c -move-> d, s -move-> t
   |
   o  i-1: a -move-> c, p -move-> s
   |
   o  i-0 initial commit: a b h p q r
   
 
 Having another branch renaming a different file to the same filename as another
 
   $ hg up 'desc("i-2")'
   1 files updated, 0 files merged, 0 files removed, 0 files unresolved
   $ hg mv b g
   $ hg ci -m 'e-1 b -move-> g'
   created new head
   $ hg mv g f
   $ hg ci -m 'e-2 g -move-> f'
   $ hg log -G --rev '::.'
   @  e-2 g -move-> f
   |
   o  e-1 b -move-> g
   |
   o  i-2: c -move-> d, s -move-> t
   |
   o  i-1: a -move-> c, p -move-> s
   |
   o  i-0 initial commit: a b h p q r
   
   $ hg up -q null
 
 Having a branch similar to the 'a' one, but moving the 'p' file around.
 
   $ hg up 'desc("i-2")'
   6 files updated, 0 files merged, 0 files removed, 0 files unresolved
   $ hg mv t u
   $ hg ci -Am 'p-1: t -move-> u'
   created new head
   $ hg mv u v
   $ hg ci -Am 'p-2: u -move-> v'
   $ hg log -G --rev '::.'
   @  p-2: u -move-> v
   |
   o  p-1: t -move-> u
   |
   o  i-2: c -move-> d, s -move-> t
   |
   o  i-1: a -move-> c, p -move-> s
   |
   o  i-0 initial commit: a b h p q r
   
   $ hg up -q null
 
 Having another branch renaming a different file to the same filename as another
 
   $ hg up 'desc("i-2")'
   6 files updated, 0 files merged, 0 files removed, 0 files unresolved
   $ hg mv r w
   $ hg ci -m 'q-1 r -move-> w'
   created new head
   $ hg mv w v
   $ hg ci -m 'q-2 w -move-> v'
   $ hg log -G --rev '::.'
   @  q-2 w -move-> v
   |
   o  q-1 r -move-> w
   |
   o  i-2: c -move-> d, s -move-> t
   |
   o  i-1: a -move-> c, p -move-> s
   |
   o  i-0 initial commit: a b h p q r
   
   $ hg up -q null
 
 Setup all merge
 ===============
 
 This is done beforehand to validate that the upgrade process creates valid copy
 information.
 
 merging with unrelated change does not interfere with the renames
 ---------------------------------------------------------------
 
 - rename on one side
 - unrelated change on the other side
 
   $ case_desc="simple merge - A side: multiple renames, B side: unrelated update"
 
   $ hg up 'desc("b-1")'
   6 files updated, 0 files merged, 0 files removed, 0 files unresolved
   $ hg merge 'desc("a-2")'
   1 files updated, 0 files merged, 1 files removed, 0 files unresolved
   (branch merge, don't forget to commit)
   $ hg ci -m "mBAm-0 $case_desc - one way"
   $ hg up 'desc("a-2")'
   1 files updated, 0 files merged, 0 files removed, 0 files unresolved
   $ hg merge 'desc("b-1")'
   1 files updated, 0 files merged, 0 files removed, 0 files unresolved
   (branch merge, don't forget to commit)
   $ hg ci -m "mABm-0 $case_desc - the other way"
   created new head
   $ hg log -G --rev '::(desc("mABm")+desc("mBAm"))'
   @    mABm-0 simple merge - A side: multiple renames, B side: unrelated update - the other way
   |\
   +---o  mBAm-0 simple merge - A side: multiple renames, B side: unrelated update - one way
   | |/
   | o  b-1: b update
   | |
   o |  a-2: e -move-> f
   | |
   o |  a-1: d -move-> e
   |/
   o  i-2: c -move-> d, s -move-> t
   |
   o  i-1: a -move-> c, p -move-> s
   |
   o  i-0 initial commit: a b h p q r
   
 
 
 merging with the side having a delete
 -------------------------------------
 
 case summary:
 - one with change to an unrelated file
 - one deleting the change
 and recreate an unrelated file after the merge
 
   $ case_desc="simple merge - C side: delete a file with copies history , B side: unrelated update"
 
   $ hg up 'desc("b-1")'
   1 files updated, 0 files merged, 1 files removed, 0 files unresolved
   $ hg merge 'desc("c-1")'
   0 files updated, 0 files merged, 1 files removed, 0 files unresolved
   (branch merge, don't forget to commit)
   $ hg ci -m "mBCm-0 $case_desc - one way"
   $ echo bar > d
   $ hg add d
   $ hg ci -m 'mBCm-1 re-add d'
   $ hg up 'desc("c-1")'
   1 files updated, 0 files merged, 1 files removed, 0 files unresolved
   $ hg merge 'desc("b-1")'
   1 files updated, 0 files merged, 0 files removed, 0 files unresolved
   (branch merge, don't forget to commit)
   $ hg ci -m "mCBm-0 $case_desc - the other way"
   created new head
   $ echo bar > d
   $ hg add d
   $ hg ci -m 'mCBm-1 re-add d'
   $ hg log -G --rev '::(desc("mCBm")+desc("mBCm"))'
   @  mCBm-1 re-add d
   |
   o    mCBm-0 simple merge - C side: delete a file with copies history , B side: unrelated update - the other way
   |\
   | | o  mBCm-1 re-add d
   | | |
   +---o  mBCm-0 simple merge - C side: delete a file with copies history , B side: unrelated update - one way
   | |/
   | o  c-1 delete d
   | |
   o |  b-1: b update
   |/
   o  i-2: c -move-> d, s -move-> t
   |
   o  i-1: a -move-> c, p -move-> s
   |
   o  i-0 initial commit: a b h p q r
   
 
 Comparing with a merge re-adding the file afterward
 ---------------------------------------------------
 
 Merge:
 - one with change to an unrelated file
 - one deleting and recreating the change
 
   $ case_desc="simple merge - B side: unrelated update, D side: delete and recreate a file (with different content)"
 
   $ hg up 'desc("b-1")'
   1 files updated, 0 files merged, 0 files removed, 0 files unresolved
   $ hg merge 'desc("d-2")'
   1 files updated, 0 files merged, 0 files removed, 0 files unresolved
   (branch merge, don't forget to commit)
   $ hg ci -m "mBDm-0 $case_desc - one way"
   $ hg up 'desc("d-2")'
   1 files updated, 0 files merged, 0 files removed, 0 files unresolved
   $ hg merge 'desc("b-1")'
   1 files updated, 0 files merged, 0 files removed, 0 files unresolved
   (branch merge, don't forget to commit)
   $ hg ci -m "mDBm-0 $case_desc - the other way"
   created new head
   $ hg log -G --rev '::(desc("mDBm")+desc("mBDm"))'
   @    mDBm-0 simple merge - B side: unrelated update, D side: delete and recreate a file (with different content) - the other way
   |\
   +---o  mBDm-0 simple merge - B side: unrelated update, D side: delete and recreate a file (with different content) - one way
   | |/
   | o  d-2 re-add d
   | |
   | o  d-1 delete d
   | |
   o |  b-1: b update
   |/
   o  i-2: c -move-> d, s -move-> t
   |
   o  i-1: a -move-> c, p -move-> s
   |
   o  i-0 initial commit: a b h p q r
   
 
 
 Comparing with a merge with colliding rename
 --------------------------------------------
 
 Subcase: new copy information on both side
 ``````````````````````````````````````````
 
 - the "e-" branch renaming b to f (through 'g')
 - the "a-" branch renaming d to f (through e)
 
   $ case_desc="merge with copies info on both side - A side: rename d to f, E side: b to f, (same content for f)"
 
   $ hg up 'desc("a-2")'
   2 files updated, 0 files merged, 1 files removed, 0 files unresolved
   $ hg merge 'desc("e-2")'
   1 files updated, 0 files merged, 1 files removed, 0 files unresolved (no-changeset !)
   0 files updated, 0 files merged, 1 files removed, 0 files unresolved (changeset !)
   (branch merge, don't forget to commit)
   $ hg ci -m "mAEm-0 $case_desc - one way"
   $ hg up 'desc("e-2")'
   2 files updated, 0 files merged, 0 files removed, 0 files unresolved (no-changeset !)
   1 files updated, 0 files merged, 0 files removed, 0 files unresolved (changeset !)
   $ hg merge 'desc("a-2")'
   1 files updated, 0 files merged, 1 files removed, 0 files unresolved (no-changeset !)
   0 files updated, 0 files merged, 1 files removed, 0 files unresolved (changeset !)
   (branch merge, don't forget to commit)
   $ hg ci -m "mEAm-0 $case_desc - the other way"
   created new head
   $ hg log -G --rev '::(desc("mAEm")+desc("mEAm"))'
   @    mEAm-0 merge with copies info on both side - A side: rename d to f, E side: b to f, (same content for f) - the other way
   |\
   +---o  mAEm-0 merge with copies info on both side - A side: rename d to f, E side: b to f, (same content for f) - one way
   | |/
   | o  e-2 g -move-> f
   | |
   | o  e-1 b -move-> g
   | |
   o |  a-2: e -move-> f
   | |
   o |  a-1: d -move-> e
   |/
   o  i-2: c -move-> d, s -move-> t
   |
   o  i-1: a -move-> c, p -move-> s
   |
   o  i-0 initial commit: a b h p q r
   
 
 Subcase: new copy information on both side with an actual merge happening
 `````````````````````````````````````````````````````````````````````````
 
 - the "p-" branch renaming 't' to 'v' (through 'u')
 - the "q-" branch renaming 'r' to 'v' (through 'w')
 
   $ case_desc="merge with copies info on both side - P side: rename t to v, Q side: r to v, (different content)"
 
   $ hg up 'desc("p-2")'
   3 files updated, 0 files merged, 2 files removed, 0 files unresolved
   $ hg merge 'desc("q-2")' --tool ':union'
   merging v
-  1 files updated, 0 files merged, 1 files removed, 0 files unresolved
+  0 files updated, 1 files merged, 1 files removed, 0 files unresolved
   (branch merge, don't forget to commit)
   $ hg ci -m "mPQm-0 $case_desc - one way"
   $ hg up 'desc("q-2")'
   2 files updated, 0 files merged, 0 files removed, 0 files unresolved
   $ hg merge 'desc("p-2")' --tool ':union'
   merging v
-  1 files updated, 0 files merged, 1 files removed, 0 files unresolved
+  0 files updated, 1 files merged, 1 files removed, 0 files unresolved
   (branch merge, don't forget to commit)
   $ hg ci -m "mQPm-0 $case_desc - the other way"
   created new head
   $ hg log -G --rev '::(desc("mAEm")+desc("mEAm"))'
   o    mEAm-0 merge with copies info on both side - A side: rename d to f, E side: b to f, (same content for f) - the other way
   |\
   +---o  mAEm-0 merge with copies info on both side - A side: rename d to f, E side: b to f, (same content for f) - one way
   | |/
   | o  e-2 g -move-> f
   | |
   | o  e-1 b -move-> g
   | |
   o |  a-2: e -move-> f
   | |
   o |  a-1: d -move-> e
   |/
   o  i-2: c -move-> d, s -move-> t
   |
   o  i-1: a -move-> c, p -move-> s
   |
   o  i-0 initial commit: a b h p q r
   
 
 Subcase: existing copy information overwritten on one branch
 ````````````````````````````````````````````````````````````
 
 Merge:
 - one with change to an unrelated file (b)
 - one overwriting a file (d) with a rename (from h to i to d)
 
   $ case_desc="simple merge - B side: unrelated change, F side: overwrite d with a copy (from h->i->d)"
 
   $ hg up 'desc("i-2")'
   2 files updated, 0 files merged, 1 files removed, 0 files unresolved
   $ hg mv h i
   $ hg commit -m "f-1: rename h -> i"
   created new head
   $ hg mv --force i d
   $ hg commit -m "f-2: rename i -> d"
   $ hg debugindex d | "$PYTHON" ../no-linkrev
      rev linkrev nodeid       p1           p2
        0       * d8252ab2e760 000000000000 000000000000 (no-changeset !)
        0       * ae258f702dfe 000000000000 000000000000 (changeset !)
        1       * b004912a8510 000000000000 000000000000
        2       * 7b79e2fe0c89 000000000000 000000000000 (no-changeset !)
   $ hg up 'desc("b-1")'
   3 files updated, 0 files merged, 0 files removed, 0 files unresolved (no-changeset !)
   2 files updated, 0 files merged, 0 files removed, 0 files unresolved (changeset !)
   $ hg merge 'desc("f-2")'
   1 files updated, 0 files merged, 1 files removed, 0 files unresolved (no-changeset !)
   0 files updated, 0 files merged, 1 files removed, 0 files unresolved (changeset !)
   (branch merge, don't forget to commit)
   $ hg ci -m "mBFm-0 $case_desc - one way"
   $ hg up 'desc("f-2")'
   1 files updated, 0 files merged, 0 files removed, 0 files unresolved
   $ hg merge 'desc("b-1")'
   1 files updated, 0 files merged, 0 files removed, 0 files unresolved
   (branch merge, don't forget to commit)
   $ hg ci -m "mFBm-0 $case_desc - the other way"
   created new head
   $ hg up null --quiet
   $ hg log -G --rev '::(desc("mBFm")+desc("mFBm"))'
   o    mFBm-0 simple merge - B side: unrelated change, F side: overwrite d with a copy (from h->i->d) - the other way
   |\
   +---o  mBFm-0 simple merge - B side: unrelated change, F side: overwrite d with a copy (from h->i->d) - one way
   | |/
   | o  f-2: rename i -> d
   | |
   | o  f-1: rename h -> i
   | |
   o |  b-1: b update
   |/
   o  i-2: c -move-> d, s -move-> t
   |
   o  i-1: a -move-> c, p -move-> s
   |
   o  i-0 initial commit: a b h p q r
   
 
 Subcase: existing copy information overwritten on one branch, with different content)
 `````````````````````````````````````````````````````````````````````````````````````
 
 Merge:
 - one with change to an unrelated file (b)
 - one overwriting a file (t) with a rename (from r to x to t), v content is not the same as on the other branch
 
   $ case_desc="simple merge - B side: unrelated change, R side: overwrite d with a copy (from r->x->t) different content"
 
   $ hg up 'desc("i-2")'
   6 files updated, 0 files merged, 0 files removed, 0 files unresolved
   $ hg mv r x
   $ hg commit -m "r-1: rename r -> x"
   created new head
   $ hg mv --force x t
   $ hg commit -m "r-2: rename t -> x"
   $ hg debugindex t | "$PYTHON" ../no-linkrev
      rev linkrev nodeid       p1           p2
        0       * d74efbf65309 000000000000 000000000000 (no-changeset !)
        1       * 02a930b9d7ad 000000000000 000000000000 (no-changeset !)
        0       * 5aed6a8dbff0 000000000000 000000000000 (changeset !)
        1       * a38b2fa17021 000000000000 000000000000 (changeset !)
   $ hg up 'desc("b-1")'
   3 files updated, 0 files merged, 0 files removed, 0 files unresolved
   $ hg merge 'desc("r-2")'
   1 files updated, 0 files merged, 1 files removed, 0 files unresolved
   (branch merge, don't forget to commit)
   $ hg ci -m "mBRm-0 $case_desc - one way"
   $ hg up 'desc("r-2")'
   1 files updated, 0 files merged, 0 files removed, 0 files unresolved
   $ hg merge 'desc("b-1")'
   1 files updated, 0 files merged, 0 files removed, 0 files unresolved
   (branch merge, don't forget to commit)
   $ hg ci -m "mRBm-0 $case_desc - the other way"
   created new head
   $ hg up null --quiet
   $ hg log -G --rev '::(desc("mBRm")+desc("mRBm"))'
   o    mRBm-0 simple merge - B side: unrelated change, R side: overwrite d with a copy (from r->x->t) different content - the other way
   |\
   +---o  mBRm-0 simple merge - B side: unrelated change, R side: overwrite d with a copy (from r->x->t) different content - one way
   | |/
   | o  r-2: rename t -> x
   | |
   | o  r-1: rename r -> x
   | |
   o |  b-1: b update
   |/
   o  i-2: c -move-> d, s -move-> t
   |
   o  i-1: a -move-> c, p -move-> s
   |
   o  i-0 initial commit: a b h p q r
   
 
 
 Subcase: reset of the copy history on one side
 ``````````````````````````````````````````````
 
 Merge:
 - one with change to a file
 - one deleting and recreating the file
 
 Unlike in the 'BD/DB' cases, an actual merge happened here. So we should
 consider history and rename on both branch of the merge.
 
   $ case_desc="actual content merge, copies on one side - D side: delete and re-add (different content), G side: update content"
 
   $ hg up 'desc("i-2")'
   6 files updated, 0 files merged, 0 files removed, 0 files unresolved
   $ echo "some update" >> d
   $ hg commit -m "g-1: update d"
   created new head
   $ hg up 'desc("d-2")'
   1 files updated, 0 files merged, 0 files removed, 0 files unresolved
   $ hg merge 'desc("g-1")' --tool :union
   merging d
-  1 files updated, 0 files merged, 0 files removed, 0 files unresolved
+  0 files updated, 1 files merged, 0 files removed, 0 files unresolved
   (branch merge, don't forget to commit)
   $ hg ci -m "mDGm-0 $case_desc - one way"
   $ hg up 'desc("g-1")'
   1 files updated, 0 files merged, 0 files removed, 0 files unresolved
   $ hg merge 'desc("d-2")' --tool :union
   merging d
-  1 files updated, 0 files merged, 0 files removed, 0 files unresolved
+  0 files updated, 1 files merged, 0 files removed, 0 files unresolved
   (branch merge, don't forget to commit)
   $ hg ci -m "mGDm-0 $case_desc - the other way"
   created new head
   $ hg log -G --rev '::(desc("mDGm")+desc("mGDm"))'
   @    mGDm-0 actual content merge, copies on one side - D side: delete and re-add (different content), G side: update content - the other way
   |\
   +---o  mDGm-0 actual content merge, copies on one side - D side: delete and re-add (different content), G side: update content - one way
   | |/
   | o  g-1: update d
   | |
   o |  d-2 re-add d
   | |
   o |  d-1 delete d
   |/
   o  i-2: c -move-> d, s -move-> t
   |
   o  i-1: a -move-> c, p -move-> s
   |
   o  i-0 initial commit: a b h p q r
   
 
 Subcase: merging a change to a file with a "copy overwrite" to that file from another branch
 ````````````````````````````````````````````````````````````````````````````````````````````
 
 Merge:
 - one with change to a file (d)
 - one overwriting that file with a rename (from h to i, to d)
 
 This case is similar to BF/FB, but an actual merge happens, so both side of the
 history are relevant.
 
 Note:
 | In this case, the merge get conflicting information since on one side we have
 | "a -> c -> d". and one the other one we have "h -> i -> d".
 |
 | The current code arbitrarily pick one side
 
   $ case_desc="merge - G side: content change, F side: copy overwrite, no content change"
 
   $ hg up 'desc("f-2")'
   1 files updated, 0 files merged, 1 files removed, 0 files unresolved
   $ hg merge 'desc("g-1")' --tool :union
   merging d (no-changeset !)
   0 files updated, 1 files merged, 0 files removed, 0 files unresolved (no-changeset !)
   1 files updated, 0 files merged, 0 files removed, 0 files unresolved (changeset !)
   (branch merge, don't forget to commit)
   $ hg ci -m "mFGm-0 $case_desc - one way"
   created new head
   $ hg up 'desc("g-1")'
   2 files updated, 0 files merged, 0 files removed, 0 files unresolved (no-changeset !)
   1 files updated, 0 files merged, 0 files removed, 0 files unresolved (changeset !)
   $ hg merge 'desc("f-2")' --tool :union
   merging d (no-changeset !)
   0 files updated, 1 files merged, 1 files removed, 0 files unresolved (no-changeset !)
   0 files updated, 0 files merged, 1 files removed, 0 files unresolved (changeset !)
   (branch merge, don't forget to commit)
   $ hg ci -m "mGFm-0 $case_desc - the other way"
   created new head
   $ hg log -G --rev '::(desc("mGFm")+desc("mFGm"))'
   @    mGFm-0 merge - G side: content change, F side: copy overwrite, no content change - the other way
   |\
   +---o  mFGm-0 merge - G side: content change, F side: copy overwrite, no content change - one way
   | |/
   | o  g-1: update d
   | |
   o |  f-2: rename i -> d
   | |
   o |  f-1: rename h -> i
   |/
   o  i-2: c -move-> d, s -move-> t
   |
   o  i-1: a -move-> c, p -move-> s
   |
   o  i-0 initial commit: a b h p q r
   
 
 
 Comparing with merging with a deletion (and keeping the file)
 -------------------------------------------------------------
 
 Merge:
 - one removing a file (d)
 - one updating that file
 - the merge keep the modified version of the file (canceling the delete)
 
 In this case, the file keep on living after the merge. So we should not drop its
 copy tracing chain.
 
   $ case_desc="merge updated/deleted - revive the file (updated content)"
 
   $ hg up 'desc("c-1")'
   1 files updated, 0 files merged, 1 files removed, 0 files unresolved
   $ hg merge 'desc("g-1")'
   file 'd' was deleted in local [working copy] but was modified in other [merge rev].
   You can use (c)hanged version, leave (d)eleted, or leave (u)nresolved.
   What do you want to do? u
   0 files updated, 0 files merged, 0 files removed, 1 files unresolved
   use 'hg resolve' to retry unresolved file merges or 'hg merge --abort' to abandon
   [1]
   $ hg resolve -t :other d
   (no more unresolved files)
   $ hg ci -m "mCGm-0 $case_desc - one way"
   created new head
 
   $ hg up 'desc("g-1")'
   0 files updated, 0 files merged, 0 files removed, 0 files unresolved
   $ hg merge 'desc("c-1")'
   file 'd' was deleted in other [merge rev] but was modified in local [working copy].
   You can use (c)hanged version, (d)elete, or leave (u)nresolved.
   What do you want to do? u
   0 files updated, 0 files merged, 0 files removed, 1 files unresolved
   use 'hg resolve' to retry unresolved file merges or 'hg merge --abort' to abandon
   [1]
   $ hg resolve -t :local d
   (no more unresolved files)
   $ hg ci -m "mGCm-0 $case_desc - the other way"
   created new head
 
   $ hg log -G --rev '::(desc("mCGm")+desc("mGCm"))'
   @    mGCm-0 merge updated/deleted - revive the file (updated content) - the other way
   |\
   +---o  mCGm-0 merge updated/deleted - revive the file (updated content) - one way
   | |/
   | o  g-1: update d
   | |
   o |  c-1 delete d
   |/
   o  i-2: c -move-> d, s -move-> t
   |
   o  i-1: a -move-> c, p -move-> s
   |
   o  i-0 initial commit: a b h p q r
   
 
 
 
 Comparing with merge restoring an untouched deleted file
 --------------------------------------------------------
 
 Merge:
 - one removing a file (d)
 - one leaving the file untouched
 - the merge actively restore the file to the same content.
 
 In this case, the file keep on living after the merge. So we should not drop its
 copy tracing chain.
 
   $ case_desc="merge explicitely revive deleted file - B side: unrelated change, C side: delete d (restored by merge)"
 
   $ hg up 'desc("c-1")'
   0 files updated, 0 files merged, 1 files removed, 0 files unresolved
   $ hg merge 'desc("b-1")'
   1 files updated, 0 files merged, 0 files removed, 0 files unresolved
   (branch merge, don't forget to commit)
   $ hg revert --rev 'desc("b-1")' d
   $ hg ci -m "mCB-revert-m-0 $case_desc - one way"
   created new head
 
   $ hg up 'desc("b-1")'
   0 files updated, 0 files merged, 0 files removed, 0 files unresolved
   $ hg merge 'desc("c-1")'
   0 files updated, 0 files merged, 1 files removed, 0 files unresolved
   (branch merge, don't forget to commit)
   $ hg revert --rev 'desc("b-1")' d
   $ hg ci -m "mBC-revert-m-0 $case_desc - the other way"
   created new head
 
   $ hg log -G --rev '::(desc("mCB-revert-m")+desc("mBC-revert-m"))'
   @    mBC-revert-m-0 merge explicitely revive deleted file - B side: unrelated change, C side: delete d (restored by merge) - the other way
   |\
   +---o  mCB-revert-m-0 merge explicitely revive deleted file - B side: unrelated change, C side: delete d (restored by merge) - one way
   | |/
   | o  c-1 delete d
   | |
   o |  b-1: b update
   |/
   o  i-2: c -move-> d, s -move-> t
   |
   o  i-1: a -move-> c, p -move-> s
   |
   o  i-0 initial commit: a b h p q r
   
 
 
   $ hg up null --quiet
 
 Merging a branch where a rename was deleted with a branch where the same file was renamed
 ------------------------------------------------------------------------------------------
 
 Create a "conflicting" merge where `d` get removed on one branch before its
 rename information actually conflict with the other branch.
 
 (the copy information from the branch that was not deleted should win).
 
   $ case_desc="simple merge - C side: d is the results of renames then deleted, H side: d is result of another rename (same content as the other branch)"
 
   $ hg up 'desc("i-0")'
   6 files updated, 0 files merged, 0 files removed, 0 files unresolved
   $ hg mv b d
   $ hg ci -m "h-1: b -(move)-> d"
   created new head
 
   $ hg up 'desc("c-1")'
   2 files updated, 0 files merged, 3 files removed, 0 files unresolved
   $ hg merge 'desc("h-1")'
   1 files updated, 0 files merged, 1 files removed, 0 files unresolved
   (branch merge, don't forget to commit)
   $ hg ci -m "mCH-delete-before-conflict-m-0 $case_desc - one way"
 
   $ hg up 'desc("h-1")'
   2 files updated, 0 files merged, 1 files removed, 0 files unresolved
   $ hg merge 'desc("c-1")'
   1 files updated, 0 files merged, 2 files removed, 0 files unresolved
   (branch merge, don't forget to commit)
   $ hg ci -m "mHC-delete-before-conflict-m-0 $case_desc - the other way"
   created new head
   $ hg log -G --rev '::(desc("mCH-delete-before-conflict-m")+desc("mHC-delete-before-conflict-m"))'
   @    mHC-delete-before-conflict-m-0 simple merge - C side: d is the results of renames then deleted, H side: d is result of another rename (same content as the other branch) - the other way
   |\
   +---o  mCH-delete-before-conflict-m-0 simple merge - C side: d is the results of renames then deleted, H side: d is result of another rename (same content as the other branch) - one way
   | |/
   | o  h-1: b -(move)-> d
   | |
   o |  c-1 delete d
   | |
   o |  i-2: c -move-> d, s -move-> t
   | |
   o |  i-1: a -move-> c, p -move-> s
   |/
   o  i-0 initial commit: a b h p q r
   
 
 Variant of previous with extra changes introduced by the merge
 --------------------------------------------------------------
 
 Multiple cases above explicitely test cases where content are the same on both side during merge. In this section we will introduce variants for theses cases where new change are introduced to these file content during the merges.
 
 
 Subcase: merge has same initial content on both side, but merge introduced a change
 ```````````````````````````````````````````````````````````````````````````````````
 
 Same as `mAEm` and `mEAm` but with extra change to the file before commiting
 
 - the "e-" branch renaming b to f (through 'g')
 - the "a-" branch renaming d to f (through e)
 
   $ case_desc="merge with file update and copies info on both side - A side: rename d to f, E side: b to f, (same content for f in parent)"
 
   $ hg up 'desc("a-2")'
   2 files updated, 0 files merged, 1 files removed, 0 files unresolved
   $ hg merge 'desc("e-2")'
   1 files updated, 0 files merged, 1 files removed, 0 files unresolved (no-changeset !)
   0 files updated, 0 files merged, 1 files removed, 0 files unresolved (changeset !)
   (branch merge, don't forget to commit)
   $ echo "content change for mAE-change-m" > f
   $ hg ci -m "mAE-change-m-0 $case_desc - one way"
   created new head
   $ hg up 'desc("e-2")'
   2 files updated, 0 files merged, 0 files removed, 0 files unresolved
   $ hg merge 'desc("a-2")'
   1 files updated, 0 files merged, 1 files removed, 0 files unresolved (no-changeset !)
   0 files updated, 0 files merged, 1 files removed, 0 files unresolved (changeset !)
   (branch merge, don't forget to commit)
   $ echo "content change for mEA-change-m" > f
   $ hg ci -m "mEA-change-m-0 $case_desc - the other way"
   created new head
   $ hg log -G --rev '::(desc("mAE-change-m")+desc("mEA-change-m"))'
   @    mEA-change-m-0 merge with file update and copies info on both side - A side: rename d to f, E side: b to f, (same content for f in parent) - the other way
   |\
   +---o  mAE-change-m-0 merge with file update and copies info on both side - A side: rename d to f, E side: b to f, (same content for f in parent) - one way
   | |/
   | o  e-2 g -move-> f
   | |
   | o  e-1 b -move-> g
   | |
   o |  a-2: e -move-> f
   | |
   o |  a-1: d -move-> e
   |/
   o  i-2: c -move-> d, s -move-> t
   |
   o  i-1: a -move-> c, p -move-> s
   |
   o  i-0 initial commit: a b h p q r
   
 
 Subcase: merge overwrite common copy information, but with extra change during the merge
 ````````````````````````````````````````````````````````````````````````````````````````
 
 Merge:
 - one with change to an unrelated file (b)
 - one overwriting a file (d) with a rename (from h to i to d)
 - the merge update f content
 
   $ case_desc="merge with extra change - B side: unrelated change, F side: overwrite d with a copy (from h->i->d)"
 
   $ hg up 'desc("f-2")'
   2 files updated, 0 files merged, 2 files removed, 0 files unresolved
 #if no-changeset
   $ hg debugindex d | "$PYTHON" ../no-linkrev
      rev linkrev nodeid       p1           p2
        0       * d8252ab2e760 000000000000 000000000000
        1       * b004912a8510 000000000000 000000000000
        2       * 7b79e2fe0c89 000000000000 000000000000
        3       * 17ec97e60577 d8252ab2e760 000000000000
        4       * 06dabf50734c b004912a8510 17ec97e60577
        5       * 19c0e3924691 17ec97e60577 b004912a8510
        6       * 89c873a01d97 7b79e2fe0c89 17ec97e60577
        7       * d55cb4e9ef57 000000000000 000000000000
 #else
   $ hg debugindex d | "$PYTHON" ../no-linkrev
      rev linkrev nodeid       p1           p2
        0       * ae258f702dfe 000000000000 000000000000
        1       * b004912a8510 000000000000 000000000000
        2       * 5cce88bf349f ae258f702dfe 000000000000
        3       * cc269dd788c8 b004912a8510 5cce88bf349f
        4       * 51c91a115080 5cce88bf349f b004912a8510
 #endif
   $ hg up 'desc("b-1")'
   3 files updated, 0 files merged, 0 files removed, 0 files unresolved (no-changeset !)
   2 files updated, 0 files merged, 0 files removed, 0 files unresolved (changeset !)
   $ hg merge 'desc("f-2")'
   1 files updated, 0 files merged, 1 files removed, 0 files unresolved (no-changeset !)
   0 files updated, 0 files merged, 1 files removed, 0 files unresolved (changeset !)
   (branch merge, don't forget to commit)
   $ echo "extra-change to (formelly h) during the merge" > d
   $ hg ci -m "mBF-change-m-0 $case_desc - one way"
   created new head
   $ hg manifest --rev . --debug | grep "  d"
   1c334238bd42ec85c6a0d83fd1b2a898a6a3215d 644   d (no-changeset !)
   cea2d99c0fde64672ef61953786fdff34f16e230 644   d (changeset !)
 
   $ hg up 'desc("f-2")'
   2 files updated, 0 files merged, 0 files removed, 0 files unresolved
   $ hg merge 'desc("b-1")'
   1 files updated, 0 files merged, 0 files removed, 0 files unresolved
   (branch merge, don't forget to commit)
   $ echo "extra-change to (formelly h) during the merge" > d
   $ hg ci -m "mFB-change-m-0 $case_desc - the other way"
   created new head
   $ hg manifest --rev . --debug | grep "  d"
   1c334238bd42ec85c6a0d83fd1b2a898a6a3215d 644   d (no-changeset !)
   cea2d99c0fde64672ef61953786fdff34f16e230 644   d (changeset !)
 #if no-changeset
   $ hg debugindex d | "$PYTHON" ../no-linkrev
      rev linkrev nodeid       p1           p2
        0       * d8252ab2e760 000000000000 000000000000
        1       * b004912a8510 000000000000 000000000000
        2       * 7b79e2fe0c89 000000000000 000000000000
        3       * 17ec97e60577 d8252ab2e760 000000000000
        4       * 06dabf50734c b004912a8510 17ec97e60577
        5       * 19c0e3924691 17ec97e60577 b004912a8510
        6       * 89c873a01d97 7b79e2fe0c89 17ec97e60577
        7       * d55cb4e9ef57 000000000000 000000000000
        8       * 1c334238bd42 7b79e2fe0c89 000000000000
 #else
   $ hg debugindex d | "$PYTHON" ../no-linkrev
      rev linkrev nodeid       p1           p2
        0       * ae258f702dfe 000000000000 000000000000
        1       * b004912a8510 000000000000 000000000000
        2       * 5cce88bf349f ae258f702dfe 000000000000
        3       * cc269dd788c8 b004912a8510 5cce88bf349f
        4       * 51c91a115080 5cce88bf349f b004912a8510
        5       * cea2d99c0fde ae258f702dfe 000000000000
 #endif
   $ hg log -G --rev '::(desc("mBF-change-m")+desc("mFB-change-m"))'
   @    mFB-change-m-0 merge with extra change - B side: unrelated change, F side: overwrite d with a copy (from h->i->d) - the other way
   |\
   +---o  mBF-change-m-0 merge with extra change - B side: unrelated change, F side: overwrite d with a copy (from h->i->d) - one way
   | |/
   | o  f-2: rename i -> d
   | |
   | o  f-1: rename h -> i
   | |
   o |  b-1: b update
   |/
   o  i-2: c -move-> d, s -move-> t
   |
   o  i-1: a -move-> c, p -move-> s
   |
   o  i-0 initial commit: a b h p q r
   
 
 Subcase: restoring and untouched deleted file, while touching it
 ````````````````````````````````````````````````````````````````
 
 Merge:
 - one removing a file (d)
 - one leaving the file untouched
 - the merge actively restore the file to the same content.
 
 In this case, the file keep on living after the merge. So we should not drop its
 copy tracing chain.
 
   $ case_desc="merge explicitely revive deleted file - B side: unrelated change, C side: delete d (restored by merge)"
 
   $ hg up 'desc("c-1")'
   2 files updated, 0 files merged, 1 files removed, 0 files unresolved
   $ hg merge 'desc("b-1")'
   1 files updated, 0 files merged, 0 files removed, 0 files unresolved
   (branch merge, don't forget to commit)
   $ hg revert --rev 'desc("b-1")' d
   $ echo "new content for d after the revert" > d
   $ hg ci -m "mCB-change-m-0 $case_desc - one way"
   created new head
   $ hg manifest --rev . --debug | grep "  d"
   e333780c17752a3b0dd15e3ad48aa4e5c745f621 644   d (no-changeset !)
   4b540a18ad699234b2b2aa18cb69555ac9c4b1df 644   d (changeset !)
 
   $ hg up 'desc("b-1")'
   1 files updated, 0 files merged, 0 files removed, 0 files unresolved
   $ hg merge 'desc("c-1")'
   0 files updated, 0 files merged, 1 files removed, 0 files unresolved
   (branch merge, don't forget to commit)
   $ hg revert --rev 'desc("b-1")' d
   $ echo "new content for d after the revert" > d
   $ hg ci -m "mBC-change-m-0 $case_desc - the other way"
   created new head
   $ hg manifest --rev . --debug | grep "  d"
   e333780c17752a3b0dd15e3ad48aa4e5c745f621 644   d (no-changeset !)
   4b540a18ad699234b2b2aa18cb69555ac9c4b1df 644   d (changeset !)
 
 
   $ hg up null --quiet
   $ hg log -G --rev '::(desc("mCB-change-m")+desc("mBC-change-m"))'
   o    mBC-change-m-0 merge explicitely revive deleted file - B side: unrelated change, C side: delete d (restored by merge) - the other way
   |\
   +---o  mCB-change-m-0 merge explicitely revive deleted file - B side: unrelated change, C side: delete d (restored by merge) - one way
   | |/
   | o  c-1 delete d
   | |
   o |  b-1: b update
   |/
   o  i-2: c -move-> d, s -move-> t
   |
   o  i-1: a -move-> c, p -move-> s
   |
   o  i-0 initial commit: a b h p q r
   
 
 Decision from previous merge are properly chained with later merge
 ------------------------------------------------------------------
 
 Subcase: chaining conflicting rename resolution
 ```````````````````````````````````````````````
 
 The "mAEm" and "mEAm" case create a rename tracking conflict on file 'f'. We
 add more change on the respective branch and merge again. These second merge
 does not involve the file 'f' and the arbitration done within "mAEm" and "mEA"
 about that file should stay unchanged.
 
 We also touch J during some of the merge to check for unrelated change to new file during merge.
 
   $ case_desc="chained merges (conflict -> simple) - same content everywhere"
 
 (extra unrelated changes)
 
   $ hg up 'desc("a-2")'
   6 files updated, 0 files merged, 0 files removed, 0 files unresolved
   $ echo j > unrelated-j
   $ hg add unrelated-j
   $ hg ci -m 'j-1: unrelated changes (based on the "a" series of changes)'
   created new head
 
   $ hg up 'desc("e-2")'
   2 files updated, 0 files merged, 2 files removed, 0 files unresolved (no-changeset !)
   1 files updated, 0 files merged, 2 files removed, 0 files unresolved (changeset !)
   $ echo k > unrelated-k
   $ hg add unrelated-k
   $ hg ci -m 'k-1: unrelated changes (based on "e" changes)'
   created new head
 
 (merge variant 1)
 
   $ hg up 'desc("mAEm")'
   1 files updated, 0 files merged, 2 files removed, 0 files unresolved (no-changeset !)
   0 files updated, 0 files merged, 2 files removed, 0 files unresolved (changeset !)
   $ hg merge 'desc("k-1")'
   1 files updated, 0 files merged, 0 files removed, 0 files unresolved
   (branch merge, don't forget to commit)
   $ hg ci -m "mAE,Km: $case_desc"
 
 (merge variant 2)
 
   $ hg up 'desc("k-1")'
   2 files updated, 0 files merged, 0 files removed, 0 files unresolved (no-changeset !)
   1 files updated, 0 files merged, 0 files removed, 0 files unresolved (changeset !)
 
   $ hg merge 'desc("mAEm")'
   1 files updated, 0 files merged, 1 files removed, 0 files unresolved (no-changeset !)
   0 files updated, 0 files merged, 1 files removed, 0 files unresolved (changeset !)
   (branch merge, don't forget to commit)
   $ hg ci -m "mK,AEm: $case_desc"
   created new head
 
 (merge variant 3)
 
   $ hg up 'desc("mEAm")'
   0 files updated, 0 files merged, 1 files removed, 0 files unresolved
   $ hg merge 'desc("j-1")'
   1 files updated, 0 files merged, 0 files removed, 0 files unresolved
   (branch merge, don't forget to commit)
   $ echo jj > unrelated-j
   $ hg ci -m "mEA,Jm: $case_desc"
 
 (merge variant 4)
 
   $ hg up 'desc("j-1")'
   3 files updated, 0 files merged, 0 files removed, 0 files unresolved (no-changeset !)
   2 files updated, 0 files merged, 0 files removed, 0 files unresolved (changeset !)
   $ hg merge 'desc("mEAm")'
   1 files updated, 0 files merged, 1 files removed, 0 files unresolved (no-changeset !)
   0 files updated, 0 files merged, 1 files removed, 0 files unresolved (changeset !)
   (branch merge, don't forget to commit)
   $ echo jj > unrelated-j
   $ hg ci -m "mJ,EAm: $case_desc"
   created new head
 
 
   $ hg log -G --rev '::(desc("mAE,Km") + desc("mK,AEm") + desc("mEA,Jm") + desc("mJ,EAm"))'
   @    mJ,EAm: chained merges (conflict -> simple) - same content everywhere
   |\
   +---o  mEA,Jm: chained merges (conflict -> simple) - same content everywhere
   | |/
   | | o    mK,AEm: chained merges (conflict -> simple) - same content everywhere
   | | |\
   | | +---o  mAE,Km: chained merges (conflict -> simple) - same content everywhere
   | | | |/
   | | | o  k-1: unrelated changes (based on "e" changes)
   | | | |
   | o | |  j-1: unrelated changes (based on the "a" series of changes)
   | | | |
   o-----+  mEAm-0 merge with copies info on both side - A side: rename d to f, E side: b to f, (same content for f) - the other way
   |/ / /
   | o /  mAEm-0 merge with copies info on both side - A side: rename d to f, E side: b to f, (same content for f) - one way
   |/|/
   | o  e-2 g -move-> f
   | |
   | o  e-1 b -move-> g
   | |
   o |  a-2: e -move-> f
   | |
   o |  a-1: d -move-> e
   |/
   o  i-2: c -move-> d, s -move-> t
   |
   o  i-1: a -move-> c, p -move-> s
   |
   o  i-0 initial commit: a b h p q r
   
 
 Subcase: chaining conflicting rename resolution, with actual merging happening
 ``````````````````````````````````````````````````````````````````````````````
 
 The "mPQm" and "mQPm" case create a rename tracking conflict on file 't'. We
 add more change on the respective branch and merge again. These second merge
 does not involve the file 't' and the arbitration done within "mPQm" and "mQP"
 about that file should stay unchanged.
 
   $ case_desc="chained merges (conflict -> simple) - different content"
 
 (extra unrelated changes)
 
   $ hg up 'desc("p-2")'
   3 files updated, 0 files merged, 3 files removed, 0 files unresolved
   $ echo s > unrelated-s
   $ hg add unrelated-s
   $ hg ci -m 's-1: unrelated changes (based on the "p" series of changes)'
   created new head
 
   $ hg up 'desc("q-2")'
   2 files updated, 0 files merged, 2 files removed, 0 files unresolved
   $ echo t > unrelated-t
   $ hg add unrelated-t
   $ hg ci -m 't-1: unrelated changes (based on "q" changes)'
   created new head
 
 (merge variant 1)
 
   $ hg up 'desc("mPQm")'
   1 files updated, 0 files merged, 2 files removed, 0 files unresolved
   $ hg merge 'desc("t-1")'
   1 files updated, 0 files merged, 0 files removed, 0 files unresolved
   (branch merge, don't forget to commit)
   $ hg ci -m "mPQ,Tm: $case_desc"
 
 (merge variant 2)
 
   $ hg up 'desc("t-1")'
   2 files updated, 0 files merged, 0 files removed, 0 files unresolved
 
   $ hg merge 'desc("mPQm")'
   1 files updated, 0 files merged, 1 files removed, 0 files unresolved
   (branch merge, don't forget to commit)
   $ hg ci -m "mT,PQm: $case_desc"
   created new head
 
 (merge variant 3)
 
   $ hg up 'desc("mQPm")'
   1 files updated, 0 files merged, 1 files removed, 0 files unresolved
   $ hg merge 'desc("s-1")'
   1 files updated, 0 files merged, 0 files removed, 0 files unresolved
   (branch merge, don't forget to commit)
   $ hg ci -m "mQP,Sm: $case_desc"
 
 (merge variant 4)
 
   $ hg up 'desc("s-1")'
   2 files updated, 0 files merged, 0 files removed, 0 files unresolved
   $ hg merge 'desc("mQPm")'
   1 files updated, 0 files merged, 1 files removed, 0 files unresolved
   (branch merge, don't forget to commit)
   $ hg ci -m "mS,QPm: $case_desc"
   created new head
   $ hg up null --quiet
 
 
   $ hg log -G --rev '::(desc("mPQ,Tm") + desc("mT,PQm") + desc("mQP,Sm") + desc("mS,QPm"))'
   o    mS,QPm: chained merges (conflict -> simple) - different content
   |\
   +---o  mQP,Sm: chained merges (conflict -> simple) - different content
   | |/
   | | o    mT,PQm: chained merges (conflict -> simple) - different content
   | | |\
   | | +---o  mPQ,Tm: chained merges (conflict -> simple) - different content
   | | | |/
   | | | o  t-1: unrelated changes (based on "q" changes)
   | | | |
   | o | |  s-1: unrelated changes (based on the "p" series of changes)
   | | | |
   o-----+  mQPm-0 merge with copies info on both side - P side: rename t to v, Q side: r to v, (different content) - the other way
   |/ / /
   | o /  mPQm-0 merge with copies info on both side - P side: rename t to v, Q side: r to v, (different content) - one way
   |/|/
   | o  q-2 w -move-> v
   | |
   | o  q-1 r -move-> w
   | |
   o |  p-2: u -move-> v
   | |
   o |  p-1: t -move-> u
   |/
   o  i-2: c -move-> d, s -move-> t
   |
   o  i-1: a -move-> c, p -move-> s
   |
   o  i-0 initial commit: a b h p q r
   
 
 Subcase: chaining salvage information during a merge
 ````````````````````````````````````````````````````
 
 We add more change on the branch were the file was deleted. merging again
 should preserve the fact eh file was salvaged.
 
   $ case_desc="chained merges (salvaged -> simple) - same content (when the file exists)"
 
 (creating the change)
 
   $ hg up 'desc("c-1")'
   5 files updated, 0 files merged, 0 files removed, 0 files unresolved
   $ echo l > unrelated-l
   $ hg add unrelated-l
   $ hg ci -m 'l-1: unrelated changes (based on "c" changes)'
   created new head
 
 (Merge variant 1)
 
   $ hg up 'desc("mBC-revert-m")'
   2 files updated, 0 files merged, 1 files removed, 0 files unresolved
   $ hg merge 'desc("l-1")'
   1 files updated, 0 files merged, 0 files removed, 0 files unresolved
   (branch merge, don't forget to commit)
   $ hg ci -m "mBC+revert,Lm: $case_desc"
 
 (Merge variant 2)
 
   $ hg up 'desc("mCB-revert-m")'
   0 files updated, 0 files merged, 1 files removed, 0 files unresolved
   $ hg merge 'desc("l-1")'
   1 files updated, 0 files merged, 0 files removed, 0 files unresolved
   (branch merge, don't forget to commit)
   $ hg ci -m "mCB+revert,Lm: $case_desc"
 
 (Merge variant 3)
 
   $ hg up 'desc("l-1")'
   1 files updated, 0 files merged, 1 files removed, 0 files unresolved
 
   $ hg merge 'desc("mBC-revert-m")'
   2 files updated, 0 files merged, 0 files removed, 0 files unresolved
   (branch merge, don't forget to commit)
   $ hg ci -m "mL,BC+revertm: $case_desc"
   created new head
 
 (Merge variant 4)
 
   $ hg up 'desc("l-1")'
   1 files updated, 0 files merged, 1 files removed, 0 files unresolved
 
   $ hg merge 'desc("mCB-revert-m")'
   2 files updated, 0 files merged, 0 files removed, 0 files unresolved
   (branch merge, don't forget to commit)
   $ hg ci -m "mL,CB+revertm: $case_desc"
   created new head
 
   $ hg log -G --rev '::(desc("mBC+revert,Lm") + desc("mCB+revert,Lm") + desc("mL,BC+revertm") + desc("mL,CB+revertm"))'
   @    mL,CB+revertm: chained merges (salvaged -> simple) - same content (when the file exists)
   |\
   | | o  mL,BC+revertm: chained merges (salvaged -> simple) - same content (when the file exists)
   | |/|
   +-+---o  mCB+revert,Lm: chained merges (salvaged -> simple) - same content (when the file exists)
   | | |
   | +---o  mBC+revert,Lm: chained merges (salvaged -> simple) - same content (when the file exists)
   | | |/
   | o |  l-1: unrelated changes (based on "c" changes)
   | | |
   | | o  mBC-revert-m-0 merge explicitely revive deleted file - B side: unrelated change, C side: delete d (restored by merge) - the other way
   | |/|
   o---+  mCB-revert-m-0 merge explicitely revive deleted file - B side: unrelated change, C side: delete d (restored by merge) - one way
   |/ /
   o |  c-1 delete d
   | |
   | o  b-1: b update
   |/
   o  i-2: c -move-> d, s -move-> t
   |
   o  i-1: a -move-> c, p -move-> s
   |
   o  i-0 initial commit: a b h p q r
   
 
 
 Subcase: chaining "merged" information during a merge
 ``````````````````````````````````````````````````````
 
 When a non-rename change are merged with a copy overwrite, the merge pick the copy source from (p1) as the reference. We should preserve this information in subsequent merges.
 
   $ case_desc="chained merges (copy-overwrite -> simple) - same content"
 
 (extra unrelated changes)
 
   $ hg up 'desc("f-2")'
   2 files updated, 0 files merged, 2 files removed, 0 files unresolved (no-changeset !)
   1 files updated, 0 files merged, 2 files removed, 0 files unresolved (changeset !)
   $ echo n > unrelated-n
   $ hg add unrelated-n
   $ hg ci -m 'n-1: unrelated changes (based on the "f" series of changes)'
   created new head
 
   $ hg up 'desc("g-1")'
   2 files updated, 0 files merged, 1 files removed, 0 files unresolved
   $ echo o > unrelated-o
   $ hg add unrelated-o
   $ hg ci -m 'o-1: unrelated changes (based on "g" changes)'
   created new head
 
 (merge variant 1)
 
   $ hg up 'desc("mFGm")'
   1 files updated, 0 files merged, 2 files removed, 0 files unresolved (no-changeset !)
   0 files updated, 0 files merged, 2 files removed, 0 files unresolved (changeset !)
   $ hg merge 'desc("o-1")'
   1 files updated, 0 files merged, 0 files removed, 0 files unresolved
   (branch merge, don't forget to commit)
   $ hg ci -m "mFG,Om: $case_desc"
 
 (merge variant 2)
 
   $ hg up 'desc("o-1")'
   2 files updated, 0 files merged, 0 files removed, 0 files unresolved (no-changeset !)
   1 files updated, 0 files merged, 0 files removed, 0 files unresolved (changeset !)
   $ hg merge 'desc("FGm")'
   1 files updated, 0 files merged, 1 files removed, 0 files unresolved (no-changeset !)
   0 files updated, 0 files merged, 1 files removed, 0 files unresolved (changeset !)
   (branch merge, don't forget to commit)
   $ hg ci -m "mO,FGm: $case_desc"
   created new head
 
 (merge variant 3)
 
   $ hg up 'desc("mGFm")'
   0 files updated, 0 files merged, 1 files removed, 0 files unresolved
   $ hg merge 'desc("n-1")'
   1 files updated, 0 files merged, 0 files removed, 0 files unresolved
   (branch merge, don't forget to commit)
   $ hg ci -m "mGF,Nm: $case_desc"
 
 (merge variant 4)
 
   $ hg up 'desc("n-1")'
   1 files updated, 0 files merged, 0 files removed, 0 files unresolved
   $ hg merge 'desc("mGFm")'
   1 files updated, 0 files merged, 0 files removed, 0 files unresolved
   (branch merge, don't forget to commit)
   $ hg ci -m "mN,GFm: $case_desc"
   created new head
 
   $ hg log -G --rev '::(desc("mFG,Om") + desc("mO,FGm") + desc("mGF,Nm") + desc("mN,GFm"))'
   @    mN,GFm: chained merges (copy-overwrite -> simple) - same content
   |\
   +---o  mGF,Nm: chained merges (copy-overwrite -> simple) - same content
   | |/
   | | o    mO,FGm: chained merges (copy-overwrite -> simple) - same content
   | | |\
   | | +---o  mFG,Om: chained merges (copy-overwrite -> simple) - same content
   | | | |/
   | | | o  o-1: unrelated changes (based on "g" changes)
   | | | |
   | o | |  n-1: unrelated changes (based on the "f" series of changes)
   | | | |
   o-----+  mGFm-0 merge - G side: content change, F side: copy overwrite, no content change - the other way
   |/ / /
   | o /  mFGm-0 merge - G side: content change, F side: copy overwrite, no content change - one way
   |/|/
   | o  g-1: update d
   | |
   o |  f-2: rename i -> d
   | |
   o |  f-1: rename h -> i
   |/
   o  i-2: c -move-> d, s -move-> t
   |
   o  i-1: a -move-> c, p -move-> s
   |
   o  i-0 initial commit: a b h p q r
   
 
 Subcase: chaining conflicting rename resolution, with extra change during the merge
 ```````````````````````````````````````````````````````````````````````````````````
 
 The "mEA-change-m-0" and "mAE-change-m-0" case create a rename tracking conflict on file 'f'. We
 add more change on the respective branch and merge again. These second merge
 does not involve the file 'f' and the arbitration done within "mAEm" and "mEA"
 about that file should stay unchanged.
 
   $ case_desc="chained merges (conflict+change -> simple) - same content on both branch in the initial merge"
 
 
 (merge variant 1)
 
   $ hg up 'desc("mAE-change-m")'
   2 files updated, 0 files merged, 3 files removed, 0 files unresolved
   $ hg merge 'desc("k-1")'
   1 files updated, 0 files merged, 0 files removed, 0 files unresolved
   (branch merge, don't forget to commit)
   $ hg ci -m "mAE-change,Km: $case_desc"
 
 (merge variant 2)
 
   $ hg up 'desc("k-1")'
   2 files updated, 0 files merged, 0 files removed, 0 files unresolved
 
   $ hg merge 'desc("mAE-change-m")'
   1 files updated, 0 files merged, 1 files removed, 0 files unresolved
   (branch merge, don't forget to commit)
   $ hg ci -m "mK,AE-change-m: $case_desc"
   created new head
 
 (merge variant 3)
 
   $ hg up 'desc("mEA-change-m")'
   1 files updated, 0 files merged, 1 files removed, 0 files unresolved
   $ hg merge 'desc("j-1")'
   1 files updated, 0 files merged, 0 files removed, 0 files unresolved
   (branch merge, don't forget to commit)
   $ hg ci -m "mEA-change,Jm: $case_desc"
 
 (merge variant 4)
 
   $ hg up 'desc("j-1")'
   2 files updated, 0 files merged, 0 files removed, 0 files unresolved
   $ hg merge 'desc("mEA-change-m")'
   1 files updated, 0 files merged, 1 files removed, 0 files unresolved
   (branch merge, don't forget to commit)
   $ hg ci -m "mJ,EA-change-m: $case_desc"
   created new head
 
 
   $ hg log -G --rev '::(desc("mAE-change,Km") + desc("mK,AE-change-m") + desc("mEA-change,Jm") + desc("mJ,EA-change-m"))'
   @    mJ,EA-change-m: chained merges (conflict+change -> simple) - same content on both branch in the initial merge
   |\
   +---o  mEA-change,Jm: chained merges (conflict+change -> simple) - same content on both branch in the initial merge
   | |/
   | | o    mK,AE-change-m: chained merges (conflict+change -> simple) - same content on both branch in the initial merge
   | | |\
   | | +---o  mAE-change,Km: chained merges (conflict+change -> simple) - same content on both branch in the initial merge
   | | | |/
   | | | o  k-1: unrelated changes (based on "e" changes)
   | | | |
   | o | |  j-1: unrelated changes (based on the "a" series of changes)
   | | | |
   o-----+  mEA-change-m-0 merge with file update and copies info on both side - A side: rename d to f, E side: b to f, (same content for f in parent) - the other way
   |/ / /
   | o /  mAE-change-m-0 merge with file update and copies info on both side - A side: rename d to f, E side: b to f, (same content for f in parent) - one way
   |/|/
   | o  e-2 g -move-> f
   | |
   | o  e-1 b -move-> g
   | |
   o |  a-2: e -move-> f
   | |
   o |  a-1: d -move-> e
   |/
   o  i-2: c -move-> d, s -move-> t
   |
   o  i-1: a -move-> c, p -move-> s
   |
   o  i-0 initial commit: a b h p q r
   
 
 Summary of all created cases
 ----------------------------
 
   $ hg up --quiet null
 
 (This exists to help keeping a compact list of the various cases we have built)
 
   $ hg log -T '{desc|firstline}\n'| sort
   a-1: d -move-> e
   a-2: e -move-> f
   b-1: b update
   c-1 delete d
   d-1 delete d
   d-2 re-add d
   e-1 b -move-> g
   e-2 g -move-> f
   f-1: rename h -> i
   f-2: rename i -> d
   g-1: update d
   h-1: b -(move)-> d
   i-0 initial commit: a b h p q r
   i-1: a -move-> c, p -move-> s
   i-2: c -move-> d, s -move-> t
   j-1: unrelated changes (based on the "a" series of changes)
   k-1: unrelated changes (based on "e" changes)
   l-1: unrelated changes (based on "c" changes)
   mABm-0 simple merge - A side: multiple renames, B side: unrelated update - the other way
   mAE,Km: chained merges (conflict -> simple) - same content everywhere
   mAE-change,Km: chained merges (conflict+change -> simple) - same content on both branch in the initial merge
   mAE-change-m-0 merge with file update and copies info on both side - A side: rename d to f, E side: b to f, (same content for f in parent) - one way
   mAEm-0 merge with copies info on both side - A side: rename d to f, E side: b to f, (same content for f) - one way
   mBAm-0 simple merge - A side: multiple renames, B side: unrelated update - one way
   mBC+revert,Lm: chained merges (salvaged -> simple) - same content (when the file exists)
   mBC-change-m-0 merge explicitely revive deleted file - B side: unrelated change, C side: delete d (restored by merge) - the other way
   mBC-revert-m-0 merge explicitely revive deleted file - B side: unrelated change, C side: delete d (restored by merge) - the other way
   mBCm-0 simple merge - C side: delete a file with copies history , B side: unrelated update - one way
   mBCm-1 re-add d
   mBDm-0 simple merge - B side: unrelated update, D side: delete and recreate a file (with different content) - one way
   mBF-change-m-0 merge with extra change - B side: unrelated change, F side: overwrite d with a copy (from h->i->d) - one way
   mBFm-0 simple merge - B side: unrelated change, F side: overwrite d with a copy (from h->i->d) - one way
   mBRm-0 simple merge - B side: unrelated change, R side: overwrite d with a copy (from r->x->t) different content - one way
   mCB+revert,Lm: chained merges (salvaged -> simple) - same content (when the file exists)
   mCB-change-m-0 merge explicitely revive deleted file - B side: unrelated change, C side: delete d (restored by merge) - one way
   mCB-revert-m-0 merge explicitely revive deleted file - B side: unrelated change, C side: delete d (restored by merge) - one way
   mCBm-0 simple merge - C side: delete a file with copies history , B side: unrelated update - the other way
   mCBm-1 re-add d
   mCGm-0 merge updated/deleted - revive the file (updated content) - one way
   mCH-delete-before-conflict-m-0 simple merge - C side: d is the results of renames then deleted, H side: d is result of another rename (same content as the other branch) - one way
   mDBm-0 simple merge - B side: unrelated update, D side: delete and recreate a file (with different content) - the other way
   mDGm-0 actual content merge, copies on one side - D side: delete and re-add (different content), G side: update content - one way
   mEA,Jm: chained merges (conflict -> simple) - same content everywhere
   mEA-change,Jm: chained merges (conflict+change -> simple) - same content on both branch in the initial merge
   mEA-change-m-0 merge with file update and copies info on both side - A side: rename d to f, E side: b to f, (same content for f in parent) - the other way
   mEAm-0 merge with copies info on both side - A side: rename d to f, E side: b to f, (same content for f) - the other way
   mFB-change-m-0 merge with extra change - B side: unrelated change, F side: overwrite d with a copy (from h->i->d) - the other way
   mFBm-0 simple merge - B side: unrelated change, F side: overwrite d with a copy (from h->i->d) - the other way
   mFG,Om: chained merges (copy-overwrite -> simple) - same content
   mFGm-0 merge - G side: content change, F side: copy overwrite, no content change - one way
   mGCm-0 merge updated/deleted - revive the file (updated content) - the other way
   mGDm-0 actual content merge, copies on one side - D side: delete and re-add (different content), G side: update content - the other way
   mGF,Nm: chained merges (copy-overwrite -> simple) - same content
   mGFm-0 merge - G side: content change, F side: copy overwrite, no content change - the other way
   mHC-delete-before-conflict-m-0 simple merge - C side: d is the results of renames then deleted, H side: d is result of another rename (same content as the other branch) - the other way
   mJ,EA-change-m: chained merges (conflict+change -> simple) - same content on both branch in the initial merge
   mJ,EAm: chained merges (conflict -> simple) - same content everywhere
   mK,AE-change-m: chained merges (conflict+change -> simple) - same content on both branch in the initial merge
   mK,AEm: chained merges (conflict -> simple) - same content everywhere
   mL,BC+revertm: chained merges (salvaged -> simple) - same content (when the file exists)
   mL,CB+revertm: chained merges (salvaged -> simple) - same content (when the file exists)
   mN,GFm: chained merges (copy-overwrite -> simple) - same content
   mO,FGm: chained merges (copy-overwrite -> simple) - same content
   mPQ,Tm: chained merges (conflict -> simple) - different content
   mPQm-0 merge with copies info on both side - P side: rename t to v, Q side: r to v, (different content) - one way
   mQP,Sm: chained merges (conflict -> simple) - different content
   mQPm-0 merge with copies info on both side - P side: rename t to v, Q side: r to v, (different content) - the other way
   mRBm-0 simple merge - B side: unrelated change, R side: overwrite d with a copy (from r->x->t) different content - the other way
   mS,QPm: chained merges (conflict -> simple) - different content
   mT,PQm: chained merges (conflict -> simple) - different content
   n-1: unrelated changes (based on the "f" series of changes)
   o-1: unrelated changes (based on "g" changes)
   p-1: t -move-> u
   p-2: u -move-> v
   q-1 r -move-> w
   q-2 w -move-> v
   r-1: rename r -> x
   r-2: rename t -> x
   s-1: unrelated changes (based on the "p" series of changes)
   t-1: unrelated changes (based on "q" changes)
 
 
 Test that sidedata computations during upgrades are correct
 ===========================================================
 
 We upgrade a repository that is not using sidedata (the filelog case) and
  check that the same side data have been generated as if they were computed at
  commit time.
 
 
 #if upgraded
   $ cat >> $HGRCPATH << EOF
   > [format]
   > exp-use-copies-side-data-changeset = yes
   > EOF
   $ hg debugformat -v | egrep 'changelog-v2|revlog-v2|copies-sdc'
   copies-sdc:          no    yes      no
   revlog-v2:           no     no      no
   changelog-v2:        no    yes      no
   $ hg debugupgraderepo --run --quiet
   upgrade will perform the following actions:
   
   requirements
      preserved: * (glob)
      added: exp-changelog-v2, exp-copies-sidedata-changeset
   
   processed revlogs:
     - all-filelogs
     - changelog
     - manifest
   
 #endif
 
 #if upgraded-parallel
   $ cat >> $HGRCPATH << EOF
   > [format]
   > exp-use-copies-side-data-changeset = yes
   > [experimental]
   > worker.repository-upgrade=yes
   > [worker]
   > enabled=yes
   > numcpus=8
   > EOF
   $ hg debugformat -v  | egrep 'changelog-v2|revlog-v2|copies-sdc'
   copies-sdc:          no    yes      no
   revlog-v2:           no     no      no
   changelog-v2:        no    yes      no
   $ hg debugupgraderepo --run --quiet
   upgrade will perform the following actions:
   
   requirements
      preserved: * (glob)
      added: exp-changelog-v2, exp-copies-sidedata-changeset
   
   processed revlogs:
     - all-filelogs
     - changelog
     - manifest
   
 #endif
 
 #if pull
   $ cd ..
   $ mv repo-chain repo-source
   $ hg init repo-chain
   $ cd repo-chain
   $ hg pull ../repo-source
   pulling from ../repo-source
   requesting all changes
   adding changesets
   adding manifests
   adding file changes
   added 80 changesets with 44 changes to 25 files (+39 heads)
   new changesets a3a31bbefea6:908ce9259ffa
   (run 'hg heads' to see heads, 'hg merge' to merge)
 #endif
 
 #if pull-upgrade
   $ cat >> $HGRCPATH << EOF
   > [format]
   > exp-use-copies-side-data-changeset = yes
   > [experimental]
   > changegroup4 = yes
   > EOF
   $ cd ..
   $ mv repo-chain repo-source
   $ hg init repo-chain
   $ cd repo-chain
   $ hg pull ../repo-source
   pulling from ../repo-source
   requesting all changes
   adding changesets
   adding manifests
   adding file changes
   added 80 changesets with 44 changes to 25 files (+39 heads)
   new changesets a3a31bbefea6:908ce9259ffa
   (run 'hg heads' to see heads, 'hg merge' to merge)
 #endif
 
 #if push
   $ cd ..
   $ mv repo-chain repo-source
   $ hg init repo-chain
   $ cd repo-source
   $ hg push ../repo-chain
   pushing to ../repo-chain
   searching for changes
   adding changesets
   adding manifests
   adding file changes
   added 80 changesets with 44 changes to 25 files (+39 heads)
   $ cd ../repo-chain
 #endif
 
 #if push-upgrade
   $ cat >> $HGRCPATH << EOF
   > [format]
   > exp-use-copies-side-data-changeset = yes
   > [experimental]
   > changegroup4 = yes
   > EOF
   $ cd ..
   $ mv repo-chain repo-source
   $ hg init repo-chain
   $ cd repo-source
   $ hg push ../repo-chain
   pushing to ../repo-chain
   searching for changes
   adding changesets
   adding manifests
   adding file changes
   added 80 changesets with 44 changes to 25 files (+39 heads)
   $ cd ../repo-chain
 #endif
 
 #if no-compatibility no-filelog no-changeset
 
   $ hg debugchangedfiles --compute 0
   added      : a, ;
   added      : b, ;
   added      : h, ;
   added      : p, ;
   added      : q, ;
   added      : r, ;
 
   $ for rev in `hg log --rev 'all()' -T '{rev}\n'`; do
   >     case_id=`hg log -r $rev -T '{word(0, desc, ":")}\n'`
   >     echo "##### revision \"$case_id\" #####"
   >     hg debugsidedata -c -v -- $rev
   >     hg debugchangedfiles $rev
   > done
   ##### revision "i-0 initial commit" #####
   1 sidedata entries
    entry-0014 size 64
     '\x00\x00\x00\x06\x04\x00\x00\x00\x01\x00\x00\x00\x00\x04\x00\x00\x00\x02\x00\x00\x00\x00\x04\x00\x00\x00\x03\x00\x00\x00\x00\x04\x00\x00\x00\x04\x00\x00\x00\x00\x04\x00\x00\x00\x05\x00\x00\x00\x00\x04\x00\x00\x00\x06\x00\x00\x00\x00abhpqr'
   added      : a, ;
   added      : b, ;
   added      : h, ;
   added      : p, ;
   added      : q, ;
   added      : r, ;
   ##### revision "i-1" #####
   1 sidedata entries
    entry-0014 size 44
     '\x00\x00\x00\x04\x0c\x00\x00\x00\x01\x00\x00\x00\x00\x06\x00\x00\x00\x02\x00\x00\x00\x00\x0c\x00\x00\x00\x03\x00\x00\x00\x00\x06\x00\x00\x00\x04\x00\x00\x00\x02acps'
   removed    : a, ;
   added    p1: c, a;
   removed    : p, ;
   added    p1: s, p;
   ##### revision "i-2" #####
   1 sidedata entries
    entry-0014 size 44
     '\x00\x00\x00\x04\x0c\x00\x00\x00\x01\x00\x00\x00\x00\x06\x00\x00\x00\x02\x00\x00\x00\x00\x0c\x00\x00\x00\x03\x00\x00\x00\x00\x06\x00\x00\x00\x04\x00\x00\x00\x02cdst'
   removed    : c, ;
   added    p1: d, c;
   removed    : s, ;
   added    p1: t, s;
   ##### revision "a-1" #####
   1 sidedata entries
    entry-0014 size 24
     '\x00\x00\x00\x02\x0c\x00\x00\x00\x01\x00\x00\x00\x00\x06\x00\x00\x00\x02\x00\x00\x00\x00de'
   removed    : d, ;
   added    p1: e, d;
   ##### revision "a-2" #####
   1 sidedata entries
    entry-0014 size 24
     '\x00\x00\x00\x02\x0c\x00\x00\x00\x01\x00\x00\x00\x00\x06\x00\x00\x00\x02\x00\x00\x00\x00ef'
   removed    : e, ;
   added    p1: f, e;
   ##### revision "b-1" #####
   1 sidedata entries
    entry-0014 size 14
     '\x00\x00\x00\x01\x14\x00\x00\x00\x01\x00\x00\x00\x00b'
   touched    : b, ;
   ##### revision "c-1 delete d" #####
   1 sidedata entries
    entry-0014 size 14
     '\x00\x00\x00\x01\x0c\x00\x00\x00\x01\x00\x00\x00\x00d'
   removed    : d, ;
   ##### revision "d-1 delete d" #####
   1 sidedata entries
    entry-0014 size 14
     '\x00\x00\x00\x01\x0c\x00\x00\x00\x01\x00\x00\x00\x00d'
   removed    : d, ;
   ##### revision "d-2 re-add d" #####
   1 sidedata entries
    entry-0014 size 14
     '\x00\x00\x00\x01\x04\x00\x00\x00\x01\x00\x00\x00\x00d'
   added      : d, ;
   ##### revision "e-1 b -move-> g" #####
   1 sidedata entries
    entry-0014 size 24
     '\x00\x00\x00\x02\x0c\x00\x00\x00\x01\x00\x00\x00\x00\x06\x00\x00\x00\x02\x00\x00\x00\x00bg'
   removed    : b, ;
   added    p1: g, b;
   ##### revision "e-2 g -move-> f" #####
   1 sidedata entries
    entry-0014 size 24
     '\x00\x00\x00\x02\x06\x00\x00\x00\x01\x00\x00\x00\x01\x0c\x00\x00\x00\x02\x00\x00\x00\x00fg'
   added    p1: f, g;
   removed    : g, ;
   ##### revision "p-1" #####
   1 sidedata entries
    entry-0014 size 24
     '\x00\x00\x00\x02\x0c\x00\x00\x00\x01\x00\x00\x00\x00\x06\x00\x00\x00\x02\x00\x00\x00\x00tu'
   removed    : t, ;
   added    p1: u, t;
   ##### revision "p-2" #####
   1 sidedata entries
    entry-0014 size 24
     '\x00\x00\x00\x02\x0c\x00\x00\x00\x01\x00\x00\x00\x00\x06\x00\x00\x00\x02\x00\x00\x00\x00uv'
   removed    : u, ;
   added    p1: v, u;
   ##### revision "q-1 r -move-> w" #####
   1 sidedata entries
    entry-0014 size 24
     '\x00\x00\x00\x02\x0c\x00\x00\x00\x01\x00\x00\x00\x00\x06\x00\x00\x00\x02\x00\x00\x00\x00rw'
   removed    : r, ;
   added    p1: w, r;
   ##### revision "q-2 w -move-> v" #####
   1 sidedata entries
    entry-0014 size 24
     '\x00\x00\x00\x02\x06\x00\x00\x00\x01\x00\x00\x00\x01\x0c\x00\x00\x00\x02\x00\x00\x00\x00vw'
   added    p1: v, w;
   removed    : w, ;
   ##### revision "mBAm-0 simple merge - A side" #####
   1 sidedata entries
    entry-0014 size 4
     '\x00\x00\x00\x00'
   ##### revision "mABm-0 simple merge - A side" #####
   1 sidedata entries
    entry-0014 size 4
     '\x00\x00\x00\x00'
   ##### revision "mBCm-0 simple merge - C side" #####
   1 sidedata entries
    entry-0014 size 4
     '\x00\x00\x00\x00'
   ##### revision "mBCm-1 re-add d" #####
   1 sidedata entries
    entry-0014 size 14
     '\x00\x00\x00\x01\x04\x00\x00\x00\x01\x00\x00\x00\x00d'
   added      : d, ;
   ##### revision "mCBm-0 simple merge - C side" #####
   1 sidedata entries
    entry-0014 size 4
     '\x00\x00\x00\x00'
   ##### revision "mCBm-1 re-add d" #####
   1 sidedata entries
    entry-0014 size 14
     '\x00\x00\x00\x01\x04\x00\x00\x00\x01\x00\x00\x00\x00d'
   added      : d, ;
   ##### revision "mBDm-0 simple merge - B side" #####
   1 sidedata entries
    entry-0014 size 4
     '\x00\x00\x00\x00'
   ##### revision "mDBm-0 simple merge - B side" #####
   1 sidedata entries
    entry-0014 size 4
     '\x00\x00\x00\x00'
   ##### revision "mAEm-0 merge with copies info on both side - A side" #####
   1 sidedata entries
    entry-0014 size 14
     '\x00\x00\x00\x01\x08\x00\x00\x00\x01\x00\x00\x00\x00f'
   merged     : f, ;
   ##### revision "mEAm-0 merge with copies info on both side - A side" #####
   1 sidedata entries
    entry-0014 size 14
     '\x00\x00\x00\x01\x08\x00\x00\x00\x01\x00\x00\x00\x00f'
   merged     : f, ;
   ##### revision "mPQm-0 merge with copies info on both side - P side" #####
   1 sidedata entries
    entry-0014 size 14
     '\x00\x00\x00\x01\x08\x00\x00\x00\x01\x00\x00\x00\x00v'
   merged     : v, ;
   ##### revision "mQPm-0 merge with copies info on both side - P side" #####
   1 sidedata entries
    entry-0014 size 14
     '\x00\x00\x00\x01\x08\x00\x00\x00\x01\x00\x00\x00\x00v'
   merged     : v, ;
   ##### revision "f-1" #####
   1 sidedata entries
    entry-0014 size 24
     '\x00\x00\x00\x02\x0c\x00\x00\x00\x01\x00\x00\x00\x00\x06\x00\x00\x00\x02\x00\x00\x00\x00hi'
   removed    : h, ;
   added    p1: i, h;
   ##### revision "f-2" #####
   1 sidedata entries
    entry-0014 size 24
     '\x00\x00\x00\x02\x16\x00\x00\x00\x01\x00\x00\x00\x01\x0c\x00\x00\x00\x02\x00\x00\x00\x00di'
   touched  p1: d, i;
   removed    : i, ;
   ##### revision "mBFm-0 simple merge - B side" #####
   1 sidedata entries
    entry-0014 size 4
     '\x00\x00\x00\x00'
   ##### revision "mFBm-0 simple merge - B side" #####
   1 sidedata entries
    entry-0014 size 4
     '\x00\x00\x00\x00'
   ##### revision "r-1" #####
   1 sidedata entries
    entry-0014 size 24
     '\x00\x00\x00\x02\x0c\x00\x00\x00\x01\x00\x00\x00\x00\x06\x00\x00\x00\x02\x00\x00\x00\x00rx'
   removed    : r, ;
   added    p1: x, r;
   ##### revision "r-2" #####
   1 sidedata entries
    entry-0014 size 24
     '\x00\x00\x00\x02\x16\x00\x00\x00\x01\x00\x00\x00\x01\x0c\x00\x00\x00\x02\x00\x00\x00\x00tx'
   touched  p1: t, x;
   removed    : x, ;
   ##### revision "mBRm-0 simple merge - B side" #####
   1 sidedata entries
    entry-0014 size 4
     '\x00\x00\x00\x00'
   ##### revision "mRBm-0 simple merge - B side" #####
   1 sidedata entries
    entry-0014 size 4
     '\x00\x00\x00\x00'
   ##### revision "g-1" #####
   1 sidedata entries
    entry-0014 size 14
     '\x00\x00\x00\x01\x14\x00\x00\x00\x01\x00\x00\x00\x00d'
   touched    : d, ;
   ##### revision "mDGm-0 actual content merge, copies on one side - D side" #####
   1 sidedata entries
    entry-0014 size 14
     '\x00\x00\x00\x01\x08\x00\x00\x00\x01\x00\x00\x00\x00d'
   merged     : d, ;
   ##### revision "mGDm-0 actual content merge, copies on one side - D side" #####
   1 sidedata entries
    entry-0014 size 14
     '\x00\x00\x00\x01\x08\x00\x00\x00\x01\x00\x00\x00\x00d'
   merged     : d, ;
   ##### revision "mFGm-0 merge - G side" #####
   1 sidedata entries
    entry-0014 size 14
     '\x00\x00\x00\x01\x08\x00\x00\x00\x01\x00\x00\x00\x00d'
   merged     : d, ;
   ##### revision "mGFm-0 merge - G side" #####
   1 sidedata entries
    entry-0014 size 14
     '\x00\x00\x00\x01\x08\x00\x00\x00\x01\x00\x00\x00\x00d'
   merged     : d, ;
   ##### revision "mCGm-0 merge updated/deleted - revive the file (updated content) - one way" #####
   1 sidedata entries
    entry-0014 size 14
     '\x00\x00\x00\x01\x10\x00\x00\x00\x01\x00\x00\x00\x00d'
   salvaged   : d, ;
   ##### revision "mGCm-0 merge updated/deleted - revive the file (updated content) - the other way" #####
   1 sidedata entries
    entry-0014 size 14
     '\x00\x00\x00\x01\x10\x00\x00\x00\x01\x00\x00\x00\x00d'
   salvaged   : d, ;
   ##### revision "mCB-revert-m-0 merge explicitely revive deleted file - B side" #####
   1 sidedata entries
    entry-0014 size 14
     '\x00\x00\x00\x01\x10\x00\x00\x00\x01\x00\x00\x00\x00d'
   salvaged   : d, ;
   ##### revision "mBC-revert-m-0 merge explicitely revive deleted file - B side" #####
   1 sidedata entries
    entry-0014 size 14
     '\x00\x00\x00\x01\x10\x00\x00\x00\x01\x00\x00\x00\x00d'
   salvaged   : d, ;
   ##### revision "h-1" #####
   1 sidedata entries
    entry-0014 size 24
     '\x00\x00\x00\x02\x0c\x00\x00\x00\x01\x00\x00\x00\x00\x06\x00\x00\x00\x02\x00\x00\x00\x00bd'
   removed    : b, ;
   added    p1: d, b;
   ##### revision "mCH-delete-before-conflict-m-0 simple merge - C side" #####
   1 sidedata entries
    entry-0014 size 4
     '\x00\x00\x00\x00'
   ##### revision "mHC-delete-before-conflict-m-0 simple merge - C side" #####
   1 sidedata entries
    entry-0014 size 4
     '\x00\x00\x00\x00'
   ##### revision "mAE-change-m-0 merge with file update and copies info on both side - A side" #####
   1 sidedata entries
    entry-0014 size 14
     '\x00\x00\x00\x01\x08\x00\x00\x00\x01\x00\x00\x00\x00f'
   merged     : f, ;
   ##### revision "mEA-change-m-0 merge with file update and copies info on both side - A side" #####
   1 sidedata entries
    entry-0014 size 14
     '\x00\x00\x00\x01\x08\x00\x00\x00\x01\x00\x00\x00\x00f'
   merged     : f, ;
   ##### revision "mBF-change-m-0 merge with extra change - B side" #####
   1 sidedata entries
    entry-0014 size 14
     '\x00\x00\x00\x01\x14\x00\x00\x00\x01\x00\x00\x00\x00d'
   touched    : d, ;
   ##### revision "mFB-change-m-0 merge with extra change - B side" #####
   1 sidedata entries
    entry-0014 size 14
     '\x00\x00\x00\x01\x14\x00\x00\x00\x01\x00\x00\x00\x00d'
   touched    : d, ;
   ##### revision "mCB-change-m-0 merge explicitely revive deleted file - B side" #####
   1 sidedata entries
    entry-0014 size 14
     '\x00\x00\x00\x01\x10\x00\x00\x00\x01\x00\x00\x00\x00d'
   salvaged   : d, ;
   ##### revision "mBC-change-m-0 merge explicitely revive deleted file - B side" #####
   1 sidedata entries
    entry-0014 size 14
     '\x00\x00\x00\x01\x10\x00\x00\x00\x01\x00\x00\x00\x00d'
   salvaged   : d, ;
   ##### revision "j-1" #####
   1 sidedata entries
    entry-0014 size 24
     '\x00\x00\x00\x01\x04\x00\x00\x00\x0b\x00\x00\x00\x00unrelated-j'
   added      : unrelated-j, ;
   ##### revision "k-1" #####
   1 sidedata entries
    entry-0014 size 24
     '\x00\x00\x00\x01\x04\x00\x00\x00\x0b\x00\x00\x00\x00unrelated-k'
   added      : unrelated-k, ;
   ##### revision "mAE,Km" #####
   1 sidedata entries
    entry-0014 size 4
     '\x00\x00\x00\x00'
   ##### revision "mK,AEm" #####
   1 sidedata entries
    entry-0014 size 4
     '\x00\x00\x00\x00'
   ##### revision "mEA,Jm" #####
   1 sidedata entries
    entry-0014 size 24
     '\x00\x00\x00\x01\x14\x00\x00\x00\x0b\x00\x00\x00\x00unrelated-j'
   touched    : unrelated-j, ;
   ##### revision "mJ,EAm" #####
   1 sidedata entries
    entry-0014 size 24
     '\x00\x00\x00\x01\x14\x00\x00\x00\x0b\x00\x00\x00\x00unrelated-j'
   touched    : unrelated-j, ;
   ##### revision "s-1" #####
   1 sidedata entries
    entry-0014 size 24
     '\x00\x00\x00\x01\x04\x00\x00\x00\x0b\x00\x00\x00\x00unrelated-s'
   added      : unrelated-s, ;
   ##### revision "t-1" #####
   1 sidedata entries
    entry-0014 size 24
     '\x00\x00\x00\x01\x04\x00\x00\x00\x0b\x00\x00\x00\x00unrelated-t'
   added      : unrelated-t, ;
   ##### revision "mPQ,Tm" #####
   1 sidedata entries
    entry-0014 size 4
     '\x00\x00\x00\x00'
   ##### revision "mT,PQm" #####
   1 sidedata entries
    entry-0014 size 4
     '\x00\x00\x00\x00'
   ##### revision "mQP,Sm" #####
   1 sidedata entries
    entry-0014 size 4
     '\x00\x00\x00\x00'
   ##### revision "mS,QPm" #####
   1 sidedata entries
    entry-0014 size 4
     '\x00\x00\x00\x00'
   ##### revision "l-1" #####
   1 sidedata entries
    entry-0014 size 24
     '\x00\x00\x00\x01\x04\x00\x00\x00\x0b\x00\x00\x00\x00unrelated-l'
   added      : unrelated-l, ;
   ##### revision "mBC+revert,Lm" #####
   1 sidedata entries
    entry-0014 size 4
     '\x00\x00\x00\x00'
   ##### revision "mCB+revert,Lm" #####
   1 sidedata entries
    entry-0014 size 4
     '\x00\x00\x00\x00'
   ##### revision "mL,BC+revertm" #####
   1 sidedata entries
    entry-0014 size 4
     '\x00\x00\x00\x00'
   ##### revision "mL,CB+revertm" #####
   1 sidedata entries
    entry-0014 size 4
     '\x00\x00\x00\x00'
   ##### revision "n-1" #####
   1 sidedata entries
    entry-0014 size 24
     '\x00\x00\x00\x01\x04\x00\x00\x00\x0b\x00\x00\x00\x00unrelated-n'
   added      : unrelated-n, ;
   ##### revision "o-1" #####
   1 sidedata entries
    entry-0014 size 24
     '\x00\x00\x00\x01\x04\x00\x00\x00\x0b\x00\x00\x00\x00unrelated-o'
   added      : unrelated-o, ;
   ##### revision "mFG,Om" #####
   1 sidedata entries
    entry-0014 size 4
     '\x00\x00\x00\x00'
   ##### revision "mO,FGm" #####
   1 sidedata entries
    entry-0014 size 4
     '\x00\x00\x00\x00'
   ##### revision "mGF,Nm" #####
   1 sidedata entries
    entry-0014 size 4
     '\x00\x00\x00\x00'
   ##### revision "mN,GFm" #####
   1 sidedata entries
    entry-0014 size 4
     '\x00\x00\x00\x00'
   ##### revision "mAE-change,Km" #####
   1 sidedata entries
    entry-0014 size 4
     '\x00\x00\x00\x00'
   ##### revision "mK,AE-change-m" #####
   1 sidedata entries
    entry-0014 size 4
     '\x00\x00\x00\x00'
   ##### revision "mEA-change,Jm" #####
   1 sidedata entries
    entry-0014 size 4
     '\x00\x00\x00\x00'
   ##### revision "mJ,EA-change-m" #####
   1 sidedata entries
    entry-0014 size 4
     '\x00\x00\x00\x00'
 
 #endif
 
 
 Test copy information chaining
 ==============================
 
 Check that matching only affect the destination and not intermediate path
 -------------------------------------------------------------------------
 
 The two status call should give the same value for f
 
   $ hg status --copies --rev 'desc("i-0")' --rev 'desc("a-2")'
   A f
     a
   A t
     p
   R a
   R p
   $ hg status --copies --rev 'desc("i-0")' --rev 'desc("a-2")' f
   A f
     a (no-changeset no-compatibility !)
 
 merging with unrelated change does not interfere with the renames
 ---------------------------------------------------------------
 
 - rename on one side
 - unrelated change on the other side
 
   $ hg log -G --rev '::(desc("mABm")+desc("mBAm"))'
   o    mABm-0 simple merge - A side: multiple renames, B side: unrelated update - the other way
   |\
   +---o  mBAm-0 simple merge - A side: multiple renames, B side: unrelated update - one way
   | |/
   | o  b-1: b update
   | |
   o |  a-2: e -move-> f
   | |
   o |  a-1: d -move-> e
   |/
   o  i-2: c -move-> d, s -move-> t
   |
   o  i-1: a -move-> c, p -move-> s
   |
   o  i-0 initial commit: a b h p q r
   
 
   $ hg status --copies --rev 'desc("b-1")' --rev 'desc("mABm")'
   A f
     d
   R d
   $ hg status --copies --rev 'desc("b-1")' --rev 'desc("mBAm")'
   A f
     d
   R d
   $ hg status --copies --rev 'desc("a-2")' --rev 'desc("mABm")'
   M b
   $ hg status --copies --rev 'desc("a-2")' --rev 'desc("mBAm")'
   M b
   $ hg status --copies --rev 'desc("i-2")' --rev 'desc("mABm")'
   M b
   A f
     d
   R d
   $ hg status --copies --rev 'desc("i-2")' --rev 'desc("mBAm")'
   M b
   A f
     d
   R d
   $ hg status --copies --rev 'desc("i-0")' --rev 'desc("mABm")'
   M b
   A f
     a
   A t
     p
   R a
   R p
   $ hg status --copies --rev 'desc("i-0")' --rev 'desc("mBAm")'
   M b
   A f
     a
   A t
     p
   R a
   R p
 
 merging with the side having a delete
 -------------------------------------
 
 case summary:
 - one with change to an unrelated file
 - one deleting the change
 and recreate an unrelated file after the merge
 
   $ hg log -G --rev '::(desc("mCBm")+desc("mBCm"))'
   o  mCBm-1 re-add d
   |
   o    mCBm-0 simple merge - C side: delete a file with copies history , B side: unrelated update - the other way
   |\
   | | o  mBCm-1 re-add d
   | | |
   +---o  mBCm-0 simple merge - C side: delete a file with copies history , B side: unrelated update - one way
   | |/
   | o  c-1 delete d
   | |
   o |  b-1: b update
   |/
   o  i-2: c -move-> d, s -move-> t
   |
   o  i-1: a -move-> c, p -move-> s
   |
   o  i-0 initial commit: a b h p q r
   
 - comparing from the merge
 
   $ hg status --copies --rev 'desc("b-1")' --rev 'desc("mBCm-0")'
   R d
   $ hg status --copies --rev 'desc("b-1")' --rev 'desc("mCBm-0")'
   R d
   $ hg status --copies --rev 'desc("c-1")' --rev 'desc("mBCm-0")'
   M b
   $ hg status --copies --rev 'desc("c-1")' --rev 'desc("mCBm-0")'
   M b
   $ hg status --copies --rev 'desc("i-2")' --rev 'desc("mBCm-0")'
   M b
   R d
   $ hg status --copies --rev 'desc("i-2")' --rev 'desc("mCBm-0")'
   M b
   R d
   $ hg status --copies --rev 'desc("i-0")' --rev 'desc("mBCm-0")'
   M b
   A t
     p
   R a
   R p
   $ hg status --copies --rev 'desc("i-0")' --rev 'desc("mCBm-0")'
   M b
   A t
     p
   R a
   R p
 
 - comparing with the merge children re-adding the file
 
   $ hg status --copies --rev 'desc("b-1")' --rev 'desc("mBCm-1")'
   M d
   $ hg status --copies --rev 'desc("b-1")' --rev 'desc("mCBm-1")'
   M d
   $ hg status --copies --rev 'desc("c-1")' --rev 'desc("mBCm-1")'
   M b
   A d
   $ hg status --copies --rev 'desc("c-1")' --rev 'desc("mCBm-1")'
   M b
   A d
   $ hg status --copies --rev 'desc("i-2")' --rev 'desc("mBCm-1")'
   M b
   M d
   $ hg status --copies --rev 'desc("i-2")' --rev 'desc("mCBm-1")'
   M b
   M d
   $ hg status --copies --rev 'desc("i-0")' --rev 'desc("mBCm-1")'
   M b
   A d
   A t
     p
   R a
   R p
   $ hg status --copies --rev 'desc("i-0")' --rev 'desc("mCBm-1")'
   M b
   A d
   A t
     p
   R a
   R p
 
 Comparing with a merge re-adding the file afterward
 ---------------------------------------------------
 
 Merge:
 - one with change to an unrelated file
 - one deleting and recreating the change
 
   $ hg log -G --rev '::(desc("mDBm")+desc("mBDm"))'
   o    mDBm-0 simple merge - B side: unrelated update, D side: delete and recreate a file (with different content) - the other way
   |\
   +---o  mBDm-0 simple merge - B side: unrelated update, D side: delete and recreate a file (with different content) - one way
   | |/
   | o  d-2 re-add d
   | |
   | o  d-1 delete d
   | |
   o |  b-1: b update
   |/
   o  i-2: c -move-> d, s -move-> t
   |
   o  i-1: a -move-> c, p -move-> s
   |
   o  i-0 initial commit: a b h p q r
   
   $ hg status --copies --rev 'desc("b-1")' --rev 'desc("mBDm-0")'
   M d
   $ hg status --copies --rev 'desc("b-1")' --rev 'desc("mDBm-0")'
   M d
   $ hg status --copies --rev 'desc("d-2")' --rev 'desc("mBDm-0")'
   M b
   $ hg status --copies --rev 'desc("d-2")' --rev 'desc("mDBm-0")'
   M b
   $ hg status --copies --rev 'desc("i-2")' --rev 'desc("mBDm-0")'
   M b
   M d
   $ hg status --copies --rev 'desc("i-2")' --rev 'desc("mDBm-0")'
   M b
   M d
 
 The bugs makes recorded copy is different depending of where we started the merge from since
 
   $ hg manifest --debug --rev 'desc("mBDm-0")' | grep '644   d'
   b004912a8510032a0350a74daa2803dadfb00e12 644   d
   $ hg manifest --debug --rev 'desc("mDBm-0")' | grep '644   d'
   b004912a8510032a0350a74daa2803dadfb00e12 644   d
 
   $ hg manifest --debug --rev 'desc("d-2")' | grep '644   d'
   b004912a8510032a0350a74daa2803dadfb00e12 644   d
   $ hg manifest --debug --rev 'desc("b-1")' | grep '644   d'
   d8252ab2e760b0d4e5288fd44cbd15a0fa567e16 644   d (no-changeset !)
   ae258f702dfeca05bf9b6a22a97a4b5645570f11 644   d (changeset !)
   $ hg debugindex d | head -n 4 | "$PYTHON" ../no-linkrev
      rev linkrev nodeid       p1           p2
        0       * d8252ab2e760 000000000000 000000000000 (no-changeset !)
        0       * ae258f702dfe 000000000000 000000000000 (changeset !)
        1       * b004912a8510 000000000000 000000000000
        2       * 7b79e2fe0c89 000000000000 000000000000 (no-changeset !)
        2       * 5cce88bf349f ae258f702dfe 000000000000 (changeset !)
 
 Log output should not include a merge commit as it did not happen
 
   $ hg log -Gfr 'desc("mBDm-0")' d
   o  d-2 re-add d
   |
   ~
 
   $ hg log -Gfr 'desc("mDBm-0")' d
   o  d-2 re-add d
   |
   ~
 
   $ hg status --copies --rev 'desc("i-0")' --rev 'desc("mBDm-0")'
   M b
   A d
   A t
     p
   R a
   R p
   $ hg status --copies --rev 'desc("i-0")' --rev 'desc("mDBm-0")'
   M b
   A d
   A t
     p
   R a
   R p
 
 
 Comparing with a merge with colliding rename
 --------------------------------------------
 
 Subcase: new copy information on both side
 ``````````````````````````````````````````
 
 - the "e-" branch renaming b to f (through 'g')
 - the "a-" branch renaming d to f (through e)
 
   $ hg log -G --rev '::(desc("mAEm")+desc("mEAm"))'
   o    mEAm-0 merge with copies info on both side - A side: rename d to f, E side: b to f, (same content for f) - the other way
   |\
   +---o  mAEm-0 merge with copies info on both side - A side: rename d to f, E side: b to f, (same content for f) - one way
   | |/
   | o  e-2 g -move-> f
   | |
   | o  e-1 b -move-> g
   | |
   o |  a-2: e -move-> f
   | |
   o |  a-1: d -move-> e
   |/
   o  i-2: c -move-> d, s -move-> t
   |
   o  i-1: a -move-> c, p -move-> s
   |
   o  i-0 initial commit: a b h p q r
   
 #if no-changeset
   $ hg manifest --debug --rev 'desc("mAEm-0")' | grep '644   f'
   2ff93c643948464ee1f871867910ae43a45b0bea 644   f
   $ hg manifest --debug --rev 'desc("mEAm-0")' | grep '644   f'
   2ff93c643948464ee1f871867910ae43a45b0bea 644   f
   $ hg manifest --debug --rev 'desc("a-2")' | grep '644   f'
   b76eb76580df486c3d51d63c5c210d4dd43a8ac7 644   f
   $ hg manifest --debug --rev 'desc("e-2")' | grep '644   f'
   e8825b386367b29fec957283a80bb47b47483fe1 644   f
   $ hg debugindex f | "$PYTHON" ../no-linkrev
      rev linkrev nodeid       p1           p2
        0       * b76eb76580df 000000000000 000000000000
        1       * e8825b386367 000000000000 000000000000
        2       * 2ff93c643948 b76eb76580df e8825b386367
        3       * 2f649fba7eb2 b76eb76580df e8825b386367
        4       * 774e7c1637d5 e8825b386367 b76eb76580df
 #else
   $ hg manifest --debug --rev 'desc("mAEm-0")' | grep '644   f'
   ae258f702dfeca05bf9b6a22a97a4b5645570f11 644   f
   $ hg manifest --debug --rev 'desc("mEAm-0")' | grep '644   f'
   ae258f702dfeca05bf9b6a22a97a4b5645570f11 644   f
   $ hg manifest --debug --rev 'desc("a-2")' | grep '644   f'
   ae258f702dfeca05bf9b6a22a97a4b5645570f11 644   f
   $ hg manifest --debug --rev 'desc("e-2")' | grep '644   f'
   ae258f702dfeca05bf9b6a22a97a4b5645570f11 644   f
   $ hg debugindex f | "$PYTHON" ../no-linkrev
      rev linkrev nodeid       p1           p2
        0       * ae258f702dfe 000000000000 000000000000
        1       * d3613c1ec831 ae258f702dfe 000000000000
        2       * 05e03c868bbc ae258f702dfe 000000000000
 #endif
 
 # Here the filelog based implementation is not looking at the rename
 # information (because the file exist on both side). However the changelog
 # based on works fine. We have different output.
 
   $ hg status --copies --rev 'desc("a-2")' --rev 'desc("mAEm-0")'
   M f (no-changeset !)
     b (no-filelog no-changeset !)
   R b
   $ hg status --copies --rev 'desc("a-2")' --rev 'desc("mEAm-0")'
   M f (no-changeset !)
     b (no-filelog no-changeset !)
   R b
   $ hg status --copies --rev 'desc("e-2")' --rev 'desc("mAEm-0")'
   M f (no-changeset !)
     d (no-filelog no-changeset !)
   R d
   $ hg status --copies --rev 'desc("e-2")' --rev 'desc("mEAm-0")'
   M f (no-changeset !)
     d (no-filelog no-changeset !)
   R d
   $ hg status --copies --rev 'desc("i-2")' --rev 'desc("a-2")'
   A f
     d
   R d
   $ hg status --copies --rev 'desc("i-2")' --rev 'desc("e-2")'
   A f
     b
   R b
 
 # From here, we run status against revision where both source file exists.
 #
 # The filelog based implementation picks an arbitrary side based on revision
 # numbers. So the same side "wins" whatever the parents order is. This is
 # sub-optimal because depending on revision numbers means the result can be
 # different from one repository to the next.
 #
 # The changeset based algorithm use the parent order to break tie on conflicting
 # information and will have a different order depending on who is p1 and p2.
 # That order is stable accross repositories. (data from p1 prevails)
 
   $ hg status --copies --rev 'desc("i-2")' --rev 'desc("mAEm-0")'
   A f
     d
   R b
   R d
   $ hg status --copies --rev 'desc("i-2")' --rev 'desc("mEAm-0")'
   A f
     d (filelog !)
     b (no-filelog !)
   R b
   R d
   $ hg status --copies --rev 'desc("i-0")' --rev 'desc("mAEm-0")'
   A f
     a
   A t
     p
   R a
   R b
   R p
   $ hg status --copies --rev 'desc("i-0")' --rev 'desc("mEAm-0")'
   A f
     a (filelog !)
     b (no-filelog !)
   A t
     p
   R a
   R b
   R p
 
 
 Subcase: existing copy information overwritten on one branch
 ````````````````````````````````````````````````````````````
 
 Note:
 | In this case, one of the merge wrongly record a merge while there is none.
 | This lead to bad copy tracing information to be dug up.
 
 
 Merge:
 - one with change to an unrelated file (b)
 - one overwriting a file (d) with a rename (from h to i to d)
 
   $ hg log -G --rev '::(desc("mBFm")+desc("mFBm"))'
   o    mFBm-0 simple merge - B side: unrelated change, F side: overwrite d with a copy (from h->i->d) - the other way
   |\
   +---o  mBFm-0 simple merge - B side: unrelated change, F side: overwrite d with a copy (from h->i->d) - one way
   | |/
   | o  f-2: rename i -> d
   | |
   | o  f-1: rename h -> i
   | |
   o |  b-1: b update
   |/
   o  i-2: c -move-> d, s -move-> t
   |
   o  i-1: a -move-> c, p -move-> s
   |
   o  i-0 initial commit: a b h p q r
   
   $ hg status --copies --rev 'desc("i-0")' --rev 'desc("mBFm-0")'
   M b
   A d
     h
   A t
     p
   R a
   R h
   R p
   $ hg status --copies --rev 'desc("i-0")' --rev 'desc("mFBm-0")'
   M b
   A d
     h
   A t
     p
   R a
   R h
   R p
   $ hg status --copies --rev 'desc("b-1")' --rev 'desc("mBFm-0")'
   M d (no-changeset !)
     h (no-filelog no-changeset !)
   R h
   $ hg status --copies --rev 'desc("f-2")' --rev 'desc("mBFm-0")'
   M b
   $ hg status --copies --rev 'desc("f-1")' --rev 'desc("mBFm-0")'
   M b
   M d (no-changeset !)
     i (no-filelog no-changeset !)
   R i
   $ hg status --copies --rev 'desc("b-1")' --rev 'desc("mFBm-0")'
   M d (no-changeset !)
     h (no-filelog no-changeset !)
   R h
   $ hg status --copies --rev 'desc("f-2")' --rev 'desc("mFBm-0")'
   M b
   $ hg status --copies --rev 'desc("f-1")' --rev 'desc("mFBm-0")'
   M b
   M d (no-changeset !)
     i (no-filelog no-changeset !)
   R i
 
 #if no-changeset
   $ hg log -Gfr 'desc("mBFm-0")' d
   o  f-2: rename i -> d
   |
   o  f-1: rename h -> i
   :
   o  i-0 initial commit: a b h p q r
   
 #else
 BROKEN: `hg log --follow <file>` relies on filelog metadata to work
   $ hg log -Gfr 'desc("mBFm-0")' d
   o  i-2: c -move-> d, s -move-> t
   |
   ~
 #endif
 
 #if no-changeset
   $ hg log -Gfr 'desc("mFBm-0")' d
   o  f-2: rename i -> d
   |
   o  f-1: rename h -> i
   :
   o  i-0 initial commit: a b h p q r
   
 #else
 BROKEN: `hg log --follow <file>` relies on filelog metadata to work
   $ hg log -Gfr 'desc("mFBm-0")' d
   o  i-2: c -move-> d, s -move-> t
   |
   ~
 #endif
 
 
 Subcase: existing copy information overwritten on one branch, with different content)
 `````````````````````````````````````````````````````````````````````````````````````
 
 Merge:
 - one with change to an unrelated file (b)
 - one overwriting a file (t) with a rename (from r to x to t), v content is not the same as on the other branch
 
   $ hg log -G --rev '::(desc("mBRm")+desc("mRBm"))'
   o    mRBm-0 simple merge - B side: unrelated change, R side: overwrite d with a copy (from r->x->t) different content - the other way
   |\
   +---o  mBRm-0 simple merge - B side: unrelated change, R side: overwrite d with a copy (from r->x->t) different content - one way
   | |/
   | o  r-2: rename t -> x
   | |
   | o  r-1: rename r -> x
   | |
   o |  b-1: b update
   |/
   o  i-2: c -move-> d, s -move-> t
   |
   o  i-1: a -move-> c, p -move-> s
   |
   o  i-0 initial commit: a b h p q r
   
   $ hg status --copies --rev 'desc("i-0")' --rev 'desc("mBRm-0")'
   M b
   A d
     a
   A t
     r
   R a
   R p
   R r
   $ hg status --copies --rev 'desc("i-0")' --rev 'desc("mRBm-0")'
   M b
   A d
     a
   A t
     r
   R a
   R p
   R r
   $ hg status --copies --rev 'desc("b-1")' --rev 'desc("mBRm-0")'
   M t
     r (no-filelog !)
   R r
   $ hg status --copies --rev 'desc("r-2")' --rev 'desc("mBRm-0")'
   M b
   $ hg status --copies --rev 'desc("r-1")' --rev 'desc("mBRm-0")'
   M b
   M t
     x (no-filelog !)
   R x
   $ hg status --copies --rev 'desc("b-1")' --rev 'desc("mRBm-0")'
   M t
     r (no-filelog !)
   R r
   $ hg status --copies --rev 'desc("r-2")' --rev 'desc("mRBm-0")'
   M b
   $ hg status --copies --rev 'desc("r-1")' --rev 'desc("mRBm-0")'
   M b
   M t
     x (no-filelog !)
   R x
 
 #if no-changeset
   $ hg log -Gfr 'desc("mBRm-0")' d
   o  i-2: c -move-> d, s -move-> t
   |
   o  i-1: a -move-> c, p -move-> s
   |
   o  i-0 initial commit: a b h p q r
   
 #else
 BROKEN: `hg log --follow <file>` relies on filelog metadata to work
   $ hg log -Gfr 'desc("mBRm-0")' d
   o  i-2: c -move-> d, s -move-> t
   |
   ~
 #endif
 
 #if no-changeset
   $ hg log -Gfr 'desc("mRBm-0")' d
   o  i-2: c -move-> d, s -move-> t
   |
   o  i-1: a -move-> c, p -move-> s
   |
   o  i-0 initial commit: a b h p q r
   
 #else
 BROKEN: `hg log --follow <file>` relies on filelog metadata to work
   $ hg log -Gfr 'desc("mRBm-0")' d
   o  i-2: c -move-> d, s -move-> t
   |
   ~
 #endif
 
 Subcase: reset of the copy history on one side
 ``````````````````````````````````````````````
 
 Merge:
 - one with change to a file
 - one deleting and recreating the file
 
 Unlike in the 'BD/DB' cases, an actual merge happened here. So we should
 consider history and rename on both branch of the merge.
 
   $ hg log -G --rev '::(desc("mDGm")+desc("mGDm"))'
   o    mGDm-0 actual content merge, copies on one side - D side: delete and re-add (different content), G side: update content - the other way
   |\
   +---o  mDGm-0 actual content merge, copies on one side - D side: delete and re-add (different content), G side: update content - one way
   | |/
   | o  g-1: update d
   | |
   o |  d-2 re-add d
   | |
   o |  d-1 delete d
   |/
   o  i-2: c -move-> d, s -move-> t
   |
   o  i-1: a -move-> c, p -move-> s
   |
   o  i-0 initial commit: a b h p q r
   
 One side of the merge have a long history with rename. The other side of the
 merge point to a new file with a smaller history. Each side is "valid".
 
 (and again the filelog based algorithm only explore one, with a pick based on
 revision numbers)
 
   $ hg status --copies --rev 'desc("i-0")' --rev 'desc("mDGm-0")'
   A d
     a (filelog !)
   A t
     p
   R a
   R p
   $ hg status --copies --rev 'desc("i-0")' --rev 'desc("mGDm-0")'
   A d
     a
   A t
     p
   R a
   R p
   $ hg status --copies --rev 'desc("d-2")' --rev 'desc("mDGm-0")'
   M d
   $ hg status --copies --rev 'desc("d-2")' --rev 'desc("mGDm-0")'
   M d
   $ hg status --copies --rev 'desc("g-1")' --rev 'desc("mDGm-0")'
   M d
   $ hg status --copies --rev 'desc("g-1")' --rev 'desc("mGDm-0")'
   M d
 
 #if no-changeset
   $ hg log -Gfr 'desc("mDGm-0")' d
   o    mDGm-0 actual content merge, copies on one side - D side: delete and re-add (different content), G side: update content - one way
   |\
   | o  g-1: update d
   | |
   o |  d-2 re-add d
   |/
   o  i-2: c -move-> d, s -move-> t
   |
   o  i-1: a -move-> c, p -move-> s
   |
   o  i-0 initial commit: a b h p q r
   
 #else
 BROKEN: `hg log --follow <file>` relies on filelog metadata to work
   $ hg log -Gfr 'desc("mDGm-0")' d
   o    mDGm-0 actual content merge, copies on one side - D side: delete and re-add (different content), G side: update content - one way
   |\
   | o  g-1: update d
   | |
   o |  d-2 re-add d
   |/
   o  i-2: c -move-> d, s -move-> t
   |
   ~
 #endif
 
 
 #if no-changeset
   $ hg log -Gfr 'desc("mDGm-0")' d
   o    mDGm-0 actual content merge, copies on one side - D side: delete and re-add (different content), G side: update content - one way
   |\
   | o  g-1: update d
   | |
   o |  d-2 re-add d
   |/
   o  i-2: c -move-> d, s -move-> t
   |
   o  i-1: a -move-> c, p -move-> s
   |
   o  i-0 initial commit: a b h p q r
   
 #else
 BROKEN: `hg log --follow <file>` relies on filelog metadata to work
   $ hg log -Gfr 'desc("mDGm-0")' d
   o    mDGm-0 actual content merge, copies on one side - D side: delete and re-add (different content), G side: update content - one way
   |\
   | o  g-1: update d
   | |
   o |  d-2 re-add d
   |/
   o  i-2: c -move-> d, s -move-> t
   |
   ~
 #endif
 
 Subcase: merging a change to a file with a "copy overwrite" to that file from another branch
 ````````````````````````````````````````````````````````````````````````````````````````````
 
 Merge:
 - one with change to a file (d)
 - one overwriting that file with a rename (from h to i, to d)
 
 This case is similar to BF/FB, but an actual merge happens, so both side of the
 history are relevant.
 
 
   $ hg log -G --rev '::(desc("mGFm")+desc("mFGm"))'
   o    mGFm-0 merge - G side: content change, F side: copy overwrite, no content change - the other way
   |\
   +---o  mFGm-0 merge - G side: content change, F side: copy overwrite, no content change - one way
   | |/
   | o  g-1: update d
   | |
   o |  f-2: rename i -> d
   | |
   o |  f-1: rename h -> i
   |/
   o  i-2: c -move-> d, s -move-> t
   |
   o  i-1: a -move-> c, p -move-> s
   |
   o  i-0 initial commit: a b h p q r
   
 
 Note:
 | In this case, the merge get conflicting information since on one side we have
 | "a -> c -> d". and one the other one we have "h -> i -> d".
 |
 | The current code arbitrarily pick one side depending the ordering of the merged hash:
 
 In this case, the file hash from "f-2" is lower, so it will be `p1` of the resulting filenode its copy tracing information will win (and trace back to "h"):
 
 Details on this hash ordering pick:
 
   $ hg manifest --debug 'desc("g-1")' | egrep 'd$'
   17ec97e605773eb44a117d1136b3849bcdc1924f 644   d (no-changeset !)
   5cce88bf349f7c742bb440f2c53f81db9c294279 644   d (changeset !)
   $ hg status --copies --rev 'desc("i-0")' --rev 'desc("g-1")' d
   A d
     a (no-changeset no-compatibility !)
 
   $ hg manifest --debug 'desc("f-2")' | egrep 'd$'
   7b79e2fe0c8924e0e598a82f048a7b024afa4d96 644   d (no-changeset !)
   ae258f702dfeca05bf9b6a22a97a4b5645570f11 644   d (changeset !)
   $ hg status --copies --rev 'desc("i-0")' --rev 'desc("f-2")' d
   A d
     h (no-changeset no-compatibility !)
 
 Copy tracing data on the resulting merge:
 
   $ hg status --copies --rev 'desc("i-0")' --rev 'desc("mFGm-0")'
   A d
     h (no-filelog !)
     a (filelog !)
   A t
     p
   R a
   R h
   R p
   $ hg status --copies --rev 'desc("i-0")' --rev 'desc("mGFm-0")'
   A d
     a (no-changeset !)
     h (changeset !)
   A t
     p
   R a
   R h
   R p
   $ hg status --copies --rev 'desc("f-2")' --rev 'desc("mFGm-0")'
   M d
   $ hg status --copies --rev 'desc("f-2")' --rev 'desc("mGFm-0")'
   M d
   $ hg status --copies --rev 'desc("f-1")' --rev 'desc("mFGm-0")'
   M d
     i (no-filelog !)
   R i
   $ hg status --copies --rev 'desc("f-1")' --rev 'desc("mGFm-0")'
   M d
     i (no-filelog !)
   R i
   $ hg status --copies --rev 'desc("g-1")' --rev 'desc("mFGm-0")'
   M d (no-changeset !)
     h (no-filelog no-changeset !)
   R h
   $ hg status --copies --rev 'desc("g-1")' --rev 'desc("mGFm-0")'
   M d (no-changeset !)
     h (no-filelog no-changeset !)
   R h
 
 #if no-changeset
   $ hg log -Gfr 'desc("mFGm-0")' d
   o    mFGm-0 merge - G side: content change, F side: copy overwrite, no content change - one way
   |\
   | o  g-1: update d
   | |
   o |  f-2: rename i -> d
   | |
   o |  f-1: rename h -> i
   |/
   o  i-2: c -move-> d, s -move-> t
   |
   o  i-1: a -move-> c, p -move-> s
   |
   o  i-0 initial commit: a b h p q r
   
 #else
 BROKEN: `hg log --follow <file>` relies on filelog metadata to work
   $ hg log -Gfr 'desc("mFGm-0")' d
   o  g-1: update d
   |
   o  i-2: c -move-> d, s -move-> t
   |
   ~
 #endif
 
 #if no-changeset
   $ hg log -Gfr 'desc("mGFm-0")' d
   o    mGFm-0 merge - G side: content change, F side: copy overwrite, no content change - the other way
   |\
   | o  g-1: update d
   | |
   o |  f-2: rename i -> d
   | |
   o |  f-1: rename h -> i
   |/
   o  i-2: c -move-> d, s -move-> t
   |
   o  i-1: a -move-> c, p -move-> s
   |
   o  i-0 initial commit: a b h p q r
   
 #else
 BROKEN: `hg log --follow <file>` relies on filelog metadata to work
   $ hg log -Gfr 'desc("mGFm-0")' d
   o  g-1: update d
   |
   o  i-2: c -move-> d, s -move-> t
   |
   ~
 #endif
 
 Subcase: new copy information on both side with an actual merge happening
 `````````````````````````````````````````````````````````````````````````
 
 - the "p-" branch renaming 't' to 'v' (through 'u')
 - the "q-" branch renaming 'r' to 'v' (through 'w')
 
 
   $ hg log -G --rev '::(desc("mPQm")+desc("mQPm"))'
   o    mQPm-0 merge with copies info on both side - P side: rename t to v, Q side: r to v, (different content) - the other way
   |\
   +---o  mPQm-0 merge with copies info on both side - P side: rename t to v, Q side: r to v, (different content) - one way
   | |/
   | o  q-2 w -move-> v
   | |
   | o  q-1 r -move-> w
   | |
   o |  p-2: u -move-> v
   | |
   o |  p-1: t -move-> u
   |/
   o  i-2: c -move-> d, s -move-> t
   |
   o  i-1: a -move-> c, p -move-> s
   |
   o  i-0 initial commit: a b h p q r
   
 
 #if no-changeset
   $ hg manifest --debug --rev 'desc("mPQm-0")' | grep '644   v'
   0946c662ef16e4e67397fd717389eb6693d41749 644   v
   $ hg manifest --debug --rev 'desc("mQPm-0")' | grep '644   v'
   0db3aad7fcc1ec27fab57060e327b9e864ea0cc9 644   v
   $ hg manifest --debug --rev 'desc("p-2")' | grep '644   v'
   3f91841cd75cadc9a1f1b4e7c1aa6d411f76032e 644   v
   $ hg manifest --debug --rev 'desc("q-2")' | grep '644   v'
   c43c088b811fd27983c0a9aadf44f3343cd4cd7e 644   v
   $ hg debugindex v | "$PYTHON" ../no-linkrev
      rev linkrev nodeid       p1           p2
        0       * 3f91841cd75c 000000000000 000000000000
        1       * c43c088b811f 000000000000 000000000000
        2       * 0946c662ef16 3f91841cd75c c43c088b811f
        3       * 0db3aad7fcc1 c43c088b811f 3f91841cd75c
 #else
   $ hg manifest --debug --rev 'desc("mPQm-0")' | grep '644   v'
   65fde9f6e4d4da23b3f610e07b53673ea9541d75 644   v
   $ hg manifest --debug --rev 'desc("mQPm-0")' | grep '644   v'
   a098dda6413aecf154eefc976afc38b295acb7e5 644   v
   $ hg manifest --debug --rev 'desc("p-2")' | grep '644   v'
   5aed6a8dbff0301328c08360d24354d3d064cf0d 644   v
   $ hg manifest --debug --rev 'desc("q-2")' | grep '644   v'
   a38b2fa170219750dac9bc7d19df831f213ba708 644   v
   $ hg debugindex v | "$PYTHON" ../no-linkrev
      rev linkrev nodeid       p1           p2
        0       * 5aed6a8dbff0 000000000000 000000000000
        1       * a38b2fa17021 000000000000 000000000000
        2       * 65fde9f6e4d4 5aed6a8dbff0 a38b2fa17021
        3       * a098dda6413a a38b2fa17021 5aed6a8dbff0
 #endif
 
 # Here the filelog based implementation is not looking at the rename
 # information (because the file exist on both side). However the changelog
 # based on works fine. We have different output.
 
   $ hg status --copies --rev 'desc("p-2")' --rev 'desc("mPQm-0")'
   M v
     r (no-filelog !)
   R r
   $ hg status --copies --rev 'desc("p-2")' --rev 'desc("mQPm-0")'
   M v
     r (no-filelog !)
   R r
   $ hg status --copies --rev 'desc("q-2")' --rev 'desc("mPQm-0")'
   M v
     t (no-filelog !)
   R t
   $ hg status --copies --rev 'desc("q-2")' --rev 'desc("mQPm-0")'
   M v
     t (no-filelog !)
   R t
   $ hg status --copies --rev 'desc("i-2")' --rev 'desc("p-2")'
   A v
     t
   R t
   $ hg status --copies --rev 'desc("i-2")' --rev 'desc("q-2")'
   A v
     r
   R r
 
 # From here, we run status against revision where both source file exists.
 #
 # The filelog based implementation picks an arbitrary side based on revision
 # numbers. So the same side "wins" whatever the parents order is. This is
 # sub-optimal because depending on revision numbers means the result can be
 # different from one repository to the next.
 #
 # The changeset based algorithm use the parent order to break tie on conflicting
 # information and will have a different order depending on who is p1 and p2.
 # That order is stable accross repositories. (data from p1 prevails)
 
   $ hg status --copies --rev 'desc("i-2")' --rev 'desc("mPQm-0")'
   A v
     t
   R r
   R t
   $ hg status --copies --rev 'desc("i-2")' --rev 'desc("mQPm-0")'
   A v
     t (filelog !)
     r (no-filelog !)
   R r
   R t
   $ hg status --copies --rev 'desc("i-0")' --rev 'desc("mPQm-0")'
   A d
     a
   A v
     r (filelog !)
     p (no-filelog !)
   R a
   R p
   R r
   $ hg status --copies --rev 'desc("i-0")' --rev 'desc("mQPm-0")'
   A d
     a
   A v
     r
   R a
   R p
   R r
 
 
 Comparing with merging with a deletion (and keeping the file)
 -------------------------------------------------------------
 
 Merge:
 - one removing a file (d)
 - one updating that file
 - the merge keep the modified version of the file (canceling the delete)
 
 In this case, the file keep on living after the merge. So we should not drop its
 copy tracing chain.
 
   $ hg log -G --rev '::(desc("mCGm")+desc("mGCm"))'
   o    mGCm-0 merge updated/deleted - revive the file (updated content) - the other way
   |\
   +---o  mCGm-0 merge updated/deleted - revive the file (updated content) - one way
   | |/
   | o  g-1: update d
   | |
   o |  c-1 delete d
   |/
   o  i-2: c -move-> d, s -move-> t
   |
   o  i-1: a -move-> c, p -move-> s
   |
   o  i-0 initial commit: a b h p q r
   
 
 'a' is the copy source of 'd'
 
   $ hg status --copies --rev 'desc("i-0")' --rev 'desc("mCGm-0")'
   A d
     a (no-compatibility no-changeset !)
   A t
     p
   R a
   R p
   $ hg status --copies --rev 'desc("i-0")' --rev 'desc("mGCm-0")'
   A d
     a (no-compatibility no-changeset !)
   A t
     p
   R a
   R p
   $ hg status --copies --rev 'desc("c-1")' --rev 'desc("mCGm-0")'
   A d
   $ hg status --copies --rev 'desc("c-1")' --rev 'desc("mGCm-0")'
   A d
   $ hg status --copies --rev 'desc("g-1")' --rev 'desc("mCGm-0")'
   $ hg status --copies --rev 'desc("g-1")' --rev 'desc("mGCm-0")'
 
 
 Comparing with merge restoring an untouched deleted file
 --------------------------------------------------------
 
 Merge:
 - one removing a file (d)
 - one leaving the file untouched
 - the merge actively restore the file to the same content.
 
 In this case, the file keep on living after the merge. So we should not drop its
 copy tracing chain.
 
   $ hg log -G --rev '::(desc("mCB-revert-m")+desc("mBC-revert-m"))'
   o    mBC-revert-m-0 merge explicitely revive deleted file - B side: unrelated change, C side: delete d (restored by merge) - the other way
   |\
   +---o  mCB-revert-m-0 merge explicitely revive deleted file - B side: unrelated change, C side: delete d (restored by merge) - one way
   | |/
   | o  c-1 delete d
   | |
   o |  b-1: b update
   |/
   o  i-2: c -move-> d, s -move-> t
   |
   o  i-1: a -move-> c, p -move-> s
   |
   o  i-0 initial commit: a b h p q r
   
 
 'a' is the the copy source of 'd'
 
   $ hg status --copies --rev 'desc("i-0")' --rev 'desc("mCB-revert-m-0")'
   M b
   A d
     a (no-compatibility no-changeset !)
   A t
     p
   R a
   R p
   $ hg status --copies --rev 'desc("i-0")' --rev 'desc("mBC-revert-m-0")'
   M b
   A d
     a (no-compatibility no-changeset !)
   A t
     p
   R a
   R p
   $ hg status --copies --rev 'desc("c-1")' --rev 'desc("mCB-revert-m-0")'
   M b
   A d
   $ hg status --copies --rev 'desc("c-1")' --rev 'desc("mBC-revert-m-0")'
   M b
   A d
   $ hg status --copies --rev 'desc("b-1")' --rev 'desc("mCB-revert-m-0")'
   $ hg status --copies --rev 'desc("b-1")' --rev 'desc("mBC-revert-m-0")'
 
 
 Merging a branch where a rename was deleted with a branch where the same file was renamed
 ------------------------------------------------------------------------------------------
 
 Create a "conflicting" merge where `d` get removed on one branch before its
 rename information actually conflict with the other branch.
 
 (the copy information from the branch that was not deleted should win).
 
   $ hg log -G --rev '::(desc("mCH-delete-before-conflict-m")+desc("mHC-delete-before-conflict-m"))'
   o    mHC-delete-before-conflict-m-0 simple merge - C side: d is the results of renames then deleted, H side: d is result of another rename (same content as the other branch) - the other way
   |\
   +---o  mCH-delete-before-conflict-m-0 simple merge - C side: d is the results of renames then deleted, H side: d is result of another rename (same content as the other branch) - one way
   | |/
   | o  h-1: b -(move)-> d
   | |
   o |  c-1 delete d
   | |
   o |  i-2: c -move-> d, s -move-> t
   | |
   o |  i-1: a -move-> c, p -move-> s
   |/
   o  i-0 initial commit: a b h p q r
   
 
   $ hg status --copies --rev 'desc("i-0")' --rev 'desc("mCH-delete-before-conflict-m")'
   A d
     b (no-compatibility no-changeset !)
   A t
     p
   R a
   R b
   R p
   $ hg status --copies --rev 'desc("i-0")' --rev 'desc("mHC-delete-before-conflict-m")'
   A d
     b
   A t
     p
   R a
   R b
   R p
   $ hg status --copies --rev 'desc("c-1")' --rev 'desc("mCH-delete-before-conflict-m")'
   A d
     b
   R b
   $ hg status --copies --rev 'desc("c-1")' --rev 'desc("mHC-delete-before-conflict-m")'
   A d
     b
   R b
   $ hg status --copies --rev 'desc("h-1")' --rev 'desc("mCH-delete-before-conflict-m")'
   A t
     p
   R a
   R p
   $ hg status --copies --rev 'desc("h-1")' --rev 'desc("mHC-delete-before-conflict-m")'
   A t
     p
   R a
   R p
 
 Variant of previous with extra changes introduced by the merge
 --------------------------------------------------------------
 
 (see case declaration for details)
 
 Subcase: merge has same initial content on both side, but merge introduced a change
 ```````````````````````````````````````````````````````````````````````````````````
 
 - the "e-" branch renaming b to f (through 'g')
 - the "a-" branch renaming d to f (through e)
 - the merge add new change to b
 
   $ hg log -G --rev '::(desc("mAE-change-m")+desc("mEA-change-m"))'
   o    mEA-change-m-0 merge with file update and copies info on both side - A side: rename d to f, E side: b to f, (same content for f in parent) - the other way
   |\
   +---o  mAE-change-m-0 merge with file update and copies info on both side - A side: rename d to f, E side: b to f, (same content for f in parent) - one way
   | |/
   | o  e-2 g -move-> f
   | |
   | o  e-1 b -move-> g
   | |
   o |  a-2: e -move-> f
   | |
   o |  a-1: d -move-> e
   |/
   o  i-2: c -move-> d, s -move-> t
   |
   o  i-1: a -move-> c, p -move-> s
   |
   o  i-0 initial commit: a b h p q r
   
 #if no-changeset
   $ hg manifest --debug --rev 'desc("mAE-change-m-0")' | grep '644   f'
   2f649fba7eb284e720d02b61f0546fcef694c045 644   f
   $ hg manifest --debug --rev 'desc("mEA-change-m-0")' | grep '644   f'
   774e7c1637d536b99e2d8ef16fd731f87a82bd09 644   f
   $ hg manifest --debug --rev 'desc("a-2")' | grep '644   f'
   b76eb76580df486c3d51d63c5c210d4dd43a8ac7 644   f
   $ hg manifest --debug --rev 'desc("e-2")' | grep '644   f'
   e8825b386367b29fec957283a80bb47b47483fe1 644   f
   $ hg debugindex f | "$PYTHON" ../no-linkrev
      rev linkrev nodeid       p1           p2
        0       * b76eb76580df 000000000000 000000000000
        1       * e8825b386367 000000000000 000000000000
        2       * 2ff93c643948 b76eb76580df e8825b386367
        3       * 2f649fba7eb2 b76eb76580df e8825b386367
        4       * 774e7c1637d5 e8825b386367 b76eb76580df
 #else
   $ hg manifest --debug --rev 'desc("mAE-change-m-0")' | grep '644   f'
   d3613c1ec8310a812ac4268fd853ac576b6caea5 644   f
   $ hg manifest --debug --rev 'desc("mEA-change-m-0")' | grep '644   f'
   05e03c868bbcab4a649cb33a238d7aa07398a469 644   f
   $ hg manifest --debug --rev 'desc("a-2")' | grep '644   f'
   ae258f702dfeca05bf9b6a22a97a4b5645570f11 644   f
   $ hg manifest --debug --rev 'desc("e-2")' | grep '644   f'
   ae258f702dfeca05bf9b6a22a97a4b5645570f11 644   f
   $ hg debugindex f | "$PYTHON" ../no-linkrev
      rev linkrev nodeid       p1           p2
        0       * ae258f702dfe 000000000000 000000000000
        1       * d3613c1ec831 ae258f702dfe 000000000000
        2       * 05e03c868bbc ae258f702dfe 000000000000
 #endif
 
 # Here the filelog based implementation is not looking at the rename
 # information (because the file exist on both side). However the changelog
 # based on works fine. We have different output.
 
   $ hg status --copies --rev 'desc("a-2")' --rev 'desc("mAE-change-m-0")'
   M f
     b (no-filelog !)
   R b
   $ hg status --copies --rev 'desc("a-2")' --rev 'desc("mEA-change-m-0")'
   M f
     b (no-filelog !)
   R b
   $ hg status --copies --rev 'desc("e-2")' --rev 'desc("mAE-change-m-0")'
   M f
     d (no-filelog !)
   R d
   $ hg status --copies --rev 'desc("e-2")' --rev 'desc("mEA-change-m-0")'
   M f
     d (no-filelog !)
   R d
   $ hg status --copies --rev 'desc("i-2")' --rev 'desc("a-2")'
   A f
     d
   R d
   $ hg status --copies --rev 'desc("i-2")' --rev 'desc("e-2")'
   A f
     b
   R b
 
 # From here, we run status against revision where both source file exists.
 #
 # The filelog based implementation picks an arbitrary side based on revision
 # numbers. So the same side "wins" whatever the parents order is. This is
 # sub-optimal because depending on revision numbers means the result can be
 # different from one repository to the next.
 #
 # The changeset based algorithm use the parent order to break tie on conflicting
 # information and will have a different order depending on who is p1 and p2.
 # That order is stable accross repositories. (data from p1 prevails)
 
   $ hg status --copies --rev 'desc("i-2")' --rev 'desc("mAE-change-m-0")'
   A f
     d
   R b
   R d
   $ hg status --copies --rev 'desc("i-2")' --rev 'desc("mEA-change-m-0")'
   A f
     d (filelog !)
     b (no-filelog !)
   R b
   R d
   $ hg status --copies --rev 'desc("i-0")' --rev 'desc("mAE-change-m-0")'
   A f
     a
   A t
     p
   R a
   R b
   R p
   $ hg status --copies --rev 'desc("i-0")' --rev 'desc("mEA-change-m-0")'
   A f
     a (filelog !)
     b (no-filelog !)
   A t
     p
   R a
   R b
   R p
 
 
 Subcase: merge overwrite common copy information, but with extra change during the merge
 ```````````````````````````````````````````````````````````````````````````````````
 
 Merge:
 - one with change to an unrelated file (b)
 - one overwriting a file (d) with a rename (from h to i to d)
 
   $ hg log -G --rev '::(desc("mBF-change-m")+desc("mFB-change-m"))'
   o    mFB-change-m-0 merge with extra change - B side: unrelated change, F side: overwrite d with a copy (from h->i->d) - the other way
   |\
   +---o  mBF-change-m-0 merge with extra change - B side: unrelated change, F side: overwrite d with a copy (from h->i->d) - one way
   | |/
   | o  f-2: rename i -> d
   | |
   | o  f-1: rename h -> i
   | |
   o |  b-1: b update
   |/
   o  i-2: c -move-> d, s -move-> t
   |
   o  i-1: a -move-> c, p -move-> s
   |
   o  i-0 initial commit: a b h p q r
   
   $ hg status --copies --rev 'desc("i-0")' --rev 'desc("mBF-change-m-0")'
   M b
   A d
     h
   A t
     p
   R a
   R h
   R p
   $ hg status --copies --rev 'desc("i-0")' --rev 'desc("mFB-change-m-0")'
   M b
   A d
     h
   A t
     p
   R a
   R h
   R p
   $ hg status --copies --rev 'desc("b-1")' --rev 'desc("mBF-change-m-0")'
   M d
     h (no-filelog !)
   R h
   $ hg status --copies --rev 'desc("f-2")' --rev 'desc("mBF-change-m-0")'
   M b
   M d
   $ hg status --copies --rev 'desc("f-1")' --rev 'desc("mBF-change-m-0")'
   M b
   M d
     i (no-filelog !)
   R i
   $ hg status --copies --rev 'desc("b-1")' --rev 'desc("mFB-change-m-0")'
   M d
     h (no-filelog !)
   R h
   $ hg status --copies --rev 'desc("f-2")' --rev 'desc("mFB-change-m-0")'
   M b
   M d
   $ hg status --copies --rev 'desc("f-1")' --rev 'desc("mFB-change-m-0")'
   M b
   M d
     i (no-filelog !)
   R i
 
 #if no-changeset
   $ hg log -Gfr 'desc("mBF-change-m-0")' d
   o    mBF-change-m-0 merge with extra change - B side: unrelated change, F side: overwrite d with a copy (from h->i->d) - one way
   |\
   o :  f-2: rename i -> d
   | :
   o :  f-1: rename h -> i
   :/
   o  i-0 initial commit: a b h p q r
   
 #else
 BROKEN: `hg log --follow <file>` relies on filelog metadata to work
   $ hg log -Gfr 'desc("mBF-change-m-0")' d
   o  mBF-change-m-0 merge with extra change - B side: unrelated change, F side: overwrite d with a copy (from h->i->d) - one way
   :
   o  i-2: c -move-> d, s -move-> t
   |
   ~
 #endif
 
 #if no-changeset
   $ hg log -Gfr 'desc("mFB-change-m-0")' d
   o    mFB-change-m-0 merge with extra change - B side: unrelated change, F side: overwrite d with a copy (from h->i->d) - the other way
   |\
   o :  f-2: rename i -> d
   | :
   o :  f-1: rename h -> i
   :/
   o  i-0 initial commit: a b h p q r
   
 #else
 BROKEN: `hg log --follow <file>` relies on filelog metadata to work
   $ hg log -Gfr 'desc("mFB-change-m-0")' d
   o  mFB-change-m-0 merge with extra change - B side: unrelated change, F side: overwrite d with a copy (from h->i->d) - the other way
   :
   o  i-2: c -move-> d, s -move-> t
   |
   ~
 #endif
 
 
 Subcase: restoring and untouched deleted file, while touching it
 ````````````````````````````````````````````````````````````````
 
 Merge:
 - one removing a file (d)
 - one leaving the file untouched
 - the merge actively restore the file to the same content.
 
 In this case, the file keep on living after the merge. So we should not drop its
 copy tracing chain.
 
   $ hg log -G --rev '::(desc("mCB-change-m")+desc("mBC-change-m"))'
   o    mBC-change-m-0 merge explicitely revive deleted file - B side: unrelated change, C side: delete d (restored by merge) - the other way
   |\
   +---o  mCB-change-m-0 merge explicitely revive deleted file - B side: unrelated change, C side: delete d (restored by merge) - one way
   | |/
   | o  c-1 delete d
   | |
   o |  b-1: b update
   |/
   o  i-2: c -move-> d, s -move-> t
   |
   o  i-1: a -move-> c, p -move-> s
   |
   o  i-0 initial commit: a b h p q r
   
 
 'a' is the the copy source of 'd'
 
   $ hg status --copies --rev 'desc("i-0")' --rev 'desc("mCB-change-m-0")'
   M b
   A d
     a (no-compatibility no-changeset !)
   A t
     p
   R a
   R p
   $ hg status --copies --rev 'desc("i-0")' --rev 'desc("mBC-change-m-0")'
   M b
   A d
     a (no-compatibility no-changeset !)
   A t
     p
   R a
   R p
   $ hg status --copies --rev 'desc("c-1")' --rev 'desc("mCB-change-m-0")'
   M b
   A d
   $ hg status --copies --rev 'desc("c-1")' --rev 'desc("mBC-change-m-0")'
   M b
   A d
   $ hg status --copies --rev 'desc("b-1")' --rev 'desc("mCB-change-m-0")'
   M d
   $ hg status --copies --rev 'desc("b-1")' --rev 'desc("mBC-change-m-0")'
   M d
 
 
 Decision from previous merge are properly chained with later merge
 ------------------------------------------------------------------
 
 
 Subcase: chaining conflicting rename resolution
 ```````````````````````````````````````````````
 
 The "mAEm" and "mEAm" case create a rename tracking conflict on file 'f'. We
 add more change on the respective branch and merge again. These second merge
 does not involve the file 'f' and the arbitration done within "mAEm" and "mEA"
 about that file should stay unchanged.
 
 The result from mAEm is the same for the subsequent merge:
 
   $ hg status --copies --rev 'desc("i-0")' --rev 'desc("mAEm")' f
   A f
     a (no-changeset no-compatibility !)
 
   $ hg status --copies --rev 'desc("i-0")' --rev 'desc("mAE,Km")' f
   A f
     a (no-changeset no-compatibility !)
 
   $ hg status --copies --rev 'desc("i-0")' --rev 'desc("mK,AEm")' f
   A f
     a (no-changeset no-compatibility !)
 
 
 The result from mEAm is the same for the subsequent merge:
 
   $ hg status --copies --rev 'desc("i-0")' --rev 'desc("mEAm")' f
   A f
     a (filelog !)
     b (no-changeset no-compatibility no-filelog !)
 
   $ hg status --copies --rev 'desc("i-0")' --rev 'desc("mEA,Jm")' f
   A f
     a (filelog !)
     b (no-changeset no-compatibility no-filelog !)
 
   $ hg status --copies --rev 'desc("i-0")' --rev 'desc("mJ,EAm")' f
   A f
     a (filelog !)
     b (no-changeset no-compatibility no-filelog !)
 
 Subcase: chaining conflicting rename resolution
 ```````````````````````````````````````````````
 
 The "mPQm" and "mQPm" case create a rename tracking conflict on file 'v'. We
 add more change on the respective branch and merge again. These second merge
 does not involve the file 'v' and the arbitration done within "mPQm" and "mQP"
 about that file should stay unchanged.
 
 The result from mPQm is the same for the subsequent merge:
 
   $ hg status --copies --rev 'desc("i-0")' --rev 'desc("mPQm")' v
   A v
     r (filelog !)
     p (no-changeset no-compatibility no-filelog !)
 
   $ hg status --copies --rev 'desc("i-0")' --rev 'desc("mPQ,Tm")' v
   A v
     r (filelog !)
     p (no-changeset no-compatibility no-filelog !)
 
   $ hg status --copies --rev 'desc("i-0")' --rev 'desc("mT,PQm")' v
   A v
     r (filelog !)
     p (no-changeset no-compatibility no-filelog !)
 
 The result from mQPm is the same for the subsequent merge:
 
   $ hg status --copies --rev 'desc("i-0")' --rev 'desc("mQPm")' v
   A v
     r (no-changeset no-compatibility !)
 
   $ hg status --copies --rev 'desc("i-0")' --rev 'desc("mQP,Sm")' v
   A v
     r (no-changeset no-compatibility !)
 
   $ hg status --copies --rev 'desc("i-0")' --rev 'desc("mS,QPm")' v
   A v
     r (filelog !)
     r (no-changeset no-compatibility no-filelog !)
 
 
 Subcase: chaining salvage information during a merge
 ````````````````````````````````````````````````````
 
 We add more change on the branch were the file was deleted. merging again
 should preserve the fact eh file was salvaged.
 
 reference output:
 
   $ hg status --copies --rev 'desc("i-0")' --rev 'desc("mCB-revert-m-0")'
   M b
   A d
     a (no-changeset no-compatibility !)
   A t
     p
   R a
   R p
   $ hg status --copies --rev 'desc("i-0")' --rev 'desc("mBC-revert-m-0")'
   M b
   A d
     a (no-changeset no-compatibility !)
   A t
     p
   R a
   R p
 
 chained output
   $ hg status --copies --rev 'desc("i-0")' --rev 'desc("mBC+revert,Lm")'
   M b
   A d
     a (no-changeset no-compatibility !)
   A t
     p
   A unrelated-l
   R a
   R p
   $ hg status --copies --rev 'desc("i-0")' --rev 'desc("mCB+revert,Lm")'
   M b
   A d
     a (no-changeset no-compatibility !)
   A t
     p
   A unrelated-l
   R a
   R p
   $ hg status --copies --rev 'desc("i-0")' --rev 'desc("mL,BC+revertm")'
   M b
   A d
     a (no-changeset no-compatibility !)
   A t
     p
   A unrelated-l
   R a
   R p
   $ hg status --copies --rev 'desc("i-0")' --rev 'desc("mL,CB+revertm")'
   M b
   A d
     a (no-changeset no-compatibility !)
   A t
     p
   A unrelated-l
   R a
   R p
 
 Subcase: chaining "merged" information during a merge
 ``````````````````````````````````````````````````````
 
 When a non-rename change are merged with a copy overwrite, the merge pick the copy source from (p1) as the reference. We should preserve this information in subsequent merges.
 
 
 reference output:
 
  (for details about the filelog pick, check the mFGm/mGFm case)
 
   $ hg status --copies --rev 'desc("i-0")' --rev 'desc("mFGm")' d
   A d
     a (filelog !)
     h (no-changeset no-compatibility no-filelog !)
   $ hg status --copies --rev 'desc("i-0")' --rev 'desc("mGFm")' d
   A d
     a (filelog !)
     a (no-changeset no-compatibility no-filelog !)
 
 Chained output
 
   $ hg status --copies --rev 'desc("i-0")' --rev 'desc("mO,FGm")' d
   A d
     a (filelog !)
     h (no-changeset no-compatibility no-filelog !)
   $ hg status --copies --rev 'desc("i-0")' --rev 'desc("mFG,Om")' d
   A d
     a (filelog !)
     h (no-changeset no-compatibility no-filelog !)
 
 
   $ hg status --copies --rev 'desc("i-0")' --rev 'desc("mGF,Nm")' d
   A d
     a (no-changeset no-compatibility !)
   $ hg status --copies --rev 'desc("i-0")' --rev 'desc("mN,GFm")' d
   A d
     a (no-changeset no-compatibility !)
 
 
 Subcase: chaining conflicting rename resolution, with extra change during the merge
 ```````````````````````````````````````````````````````````````````````````````````
 
 The "mAEm" and "mEAm" case create a rename tracking conflict on file 'f'. We
 add more change on the respective branch and merge again. These second merge
 does not involve the file 'f' and the arbitration done within "mAEm" and "mEA"
 about that file should stay unchanged.
 
 The result from mAEm is the same for the subsequent merge:
 
   $ hg status --copies --rev 'desc("i-0")' --rev 'desc("mAE-change-m")' f
   A f
     a (no-changeset no-compatibility !)
 
   $ hg status --copies --rev 'desc("i-0")' --rev 'desc("mAE-change,Km")' f
   A f
     a (no-changeset no-compatibility !)
 
   $ hg status --copies --rev 'desc("i-0")' --rev 'desc("mK,AE-change-m")' f
   A f
     a (no-changeset no-compatibility !)
 
 
 The result from mEAm is the same for the subsequent merge:
 
   $ hg status --copies --rev 'desc("i-0")' --rev 'desc("mEA-change-m")' f
   A f
     a (filelog !)
     b (no-changeset no-compatibility no-filelog !)
 
   $ hg status --copies --rev 'desc("i-0")' --rev 'desc("mEA-change,Jm")' f
   A f
     a (filelog !)
     b (no-changeset no-compatibility no-filelog !)
 
   $ hg status --copies --rev 'desc("i-0")' --rev 'desc("mJ,EA-change-m")' f
   A f
     a (filelog !)
     b (no-changeset no-compatibility no-filelog !)

tests/test-merge-internal-tools-pattern.t

@@ -1,141 +1,141 b''
 Make sure that the internal merge tools (internal:fail, internal:local,
 internal:union and internal:other) are used when matched by a
 merge-pattern in hgrc
 
 Make sure HGMERGE doesn't interfere with the test:
 
   $ unset HGMERGE
 
   $ hg init
 
 Initial file contents:
 
   $ echo "line 1" > f
   $ echo "line 2" >> f
   $ echo "line 3" >> f
   $ hg ci -Am "revision 0"
   adding f
 
   $ cat f
   line 1
   line 2
   line 3
 
 Branch 1: editing line 1:
 
   $ sed 's/line 1/first line/' f > f.new
   $ mv f.new f
   $ hg ci -Am "edited first line"
 
 Branch 2: editing line 3:
 
   $ hg update 0
   1 files updated, 0 files merged, 0 files removed, 0 files unresolved
   $ sed 's/line 3/third line/' f > f.new
   $ mv f.new f
   $ hg ci -Am "edited third line"
   created new head
 
 Merge using internal:fail tool:
 
   $ echo "[merge-patterns]" > .hg/hgrc
   $ echo "* = internal:fail" >> .hg/hgrc
 
   $ hg merge
   0 files updated, 0 files merged, 0 files removed, 1 files unresolved
   use 'hg resolve' to retry unresolved file merges or 'hg merge --abort' to abandon
   [1]
 
   $ cat f
   line 1
   line 2
   third line
 
   $ hg stat
   M f
 
 Merge using internal:local tool:
 
   $ hg update -C 2
   1 files updated, 0 files merged, 0 files removed, 0 files unresolved
   $ sed 's/internal:fail/internal:local/' .hg/hgrc > .hg/hgrc.new
   $ mv .hg/hgrc.new .hg/hgrc
 
   $ hg merge
   0 files updated, 1 files merged, 0 files removed, 0 files unresolved
   (branch merge, don't forget to commit)
 
   $ cat f
   line 1
   line 2
   third line
 
   $ hg stat
   M f
 
 Merge using internal:other tool:
 
   $ hg update -C 2
   1 files updated, 0 files merged, 0 files removed, 0 files unresolved
   $ sed 's/internal:local/internal:other/' .hg/hgrc > .hg/hgrc.new
   $ mv .hg/hgrc.new .hg/hgrc
 
   $ hg merge
   0 files updated, 1 files merged, 0 files removed, 0 files unresolved
   (branch merge, don't forget to commit)
 
   $ cat f
   first line
   line 2
   line 3
 
   $ hg stat
   M f
 
 Merge using default tool:
 
   $ hg update -C 2
   1 files updated, 0 files merged, 0 files removed, 0 files unresolved
   $ rm .hg/hgrc
 
   $ hg merge
   merging f
   0 files updated, 1 files merged, 0 files removed, 0 files unresolved
   (branch merge, don't forget to commit)
 
   $ cat f
   first line
   line 2
   third line
 
   $ hg stat
   M f
 
 Merge using internal:union tool:
 
   $ hg update -C 2
   1 files updated, 0 files merged, 0 files removed, 0 files unresolved
 
   $ echo "line 4a" >>f
   $ hg ci -Am "Adding fourth line (commit 4)"
   $ hg update 2
   1 files updated, 0 files merged, 0 files removed, 0 files unresolved
 
   $ echo "line 4b" >>f
   $ hg ci -Am "Adding fourth line v2 (commit 5)"
   created new head
 
   $ echo "[merge-patterns]" > .hg/hgrc
   $ echo "* = internal:union" >> .hg/hgrc
 
   $ hg merge 3
   merging f
-  1 files updated, 0 files merged, 0 files removed, 0 files unresolved
+  0 files updated, 1 files merged, 0 files removed, 0 files unresolved
   (branch merge, don't forget to commit)
 
   $ cat f
   line 1
   line 2
   third line
   line 4b
   line 4a