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

     2

     3

  $ echo 123 > a

     4

  $ hg add a

     5

  $ hg commit -m "first" a

     6

     7

  $ mkdir sub

     8

  $ echo 321 > sub/b

     9

  $ hg add sub/b

    10

  $ hg commit -m "second" sub/b

    11

    12

  $ cat sub/b

    13

  321

    14

    15

  $ hg co 0

    16

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

    17

    18

  $ cat sub/b 2>/dev/null || echo "sub/b not present"

    19

  sub/b not present

    20

    21

  $ test -d sub || echo "sub not present"

    22

  sub not present

    23