merge: move almost all change/delete conflicts to resolve phase (BC) (API) We have finally laid all the groundwork to make this happen. The only change/delete conflicts that haven't been moved are .hgsubstate conflicts. Those are trickier to deal with and well outside the scope of this series. We add comprehensive testing not just for the initial selections but also for re-resolves and all possible dirstate transitions caused by merge tools. That testing managed to shake out several bugs in the way we were handling dirstate transitions. The other test changes are because we now treat change/delete conflicts as proper merges, and increment the 'merged' counter rather than the 'updated' counter. I believe this is the right approach here. For third-party extensions, if they're interacting with filemerge code they might have to deal with an absentfilectx rather than a regular filectx. Still to come: - add a 'leave unresolved' option to merges - change the default for non-interactive change/delete conflicts to be 'leave unresolved' - add debug output to go alongside debug outputs for binary and symlink file merges

     1

  $ hg init repo

     2

  $ cd repo

     3

     4

  $ touch foo

     5

  $ hg ci -Am 'add foo'

     6

  adding foo

     7

     8

  $ hg up -C null

     9

  0 files updated, 0 files merged, 1 files removed, 0 files unresolved

    10

    11

this should be stored as a delta against rev 0

    12

    13

  $ echo foo bar baz > foo

    14

  $ hg ci -Am 'add foo again'

    15

  adding foo

    16

  created new head

    17

    18

  $ hg debugindex foo

    19

     rev    offset  length  ..... linkrev nodeid       p1           p2 (re)

    20

       0         0       0  .....       0 b80de5d13875 000000000000 000000000000 (re)

    21

       1         0      13  .....       1 0376abec49b8 000000000000 000000000000 (re)

    22

    23

  $ cd ..