evolve: handle stabilization of merge changeset with both parents obsoleted This patch adds logic to stabilize an orphan merge changeset having both parents obsoleted. The logic tries to first stabilize the merge changeset on successor of second parent and then stabilize the new changeset formed on the successor of first parent. We are stabilizing on second parent first and then to second parent to preserve the first parent's successor as first parent of the merge changeset. Conflicts can occcur and we can loose processing information, therefore we store a variable in statefile `orphanmerge` which represents whether we are processing a merge changeset with both parents obsoleted. Thanks to Pierre-Yves David for suggesting this way and helping to understand the correctness of this. More rigourous test cases for this will be added in next patch.

     1

#require test-repo

     2

     3

  $ checkcm() {

     4

  >   if ! (which check-manifest > /dev/null); then

     5

  >     echo skipped: missing tool: check-manifest;

     6

  >     exit 80;

     7

  >   fi;

     8

  > };

     9

  $ checkcm

    10

  $ cat << EOF >> $HGRCPATH

    11

  > [experimental]

    12

  > evolution=all

    13

  > EOF

    14

    15

Run check manifest:

    16

    17

  $ cd $TESTDIR/..

    18

  $ check-manifest

    19

  lists of files in version control and sdist match