next: solve the issue of `next` get confused by split This patch solve a problem of next command which get confused by split. Let me describe how it was getting confused: Initial state of repo: A---B---C After splitting B to (B1,B2): @ A---B1---B2 \ ---B---C X * (note: C is orphan; checkedout to B1) Lets make an amend on B1: @ B1' / A---B1---B2 \ X * \ ---B---C X * Now, if run `hg next` (--evolve is True by default now): $ it would give you choice to choose from B2 and C thinking that C could also be a possbile children for B1, instead of stablizing B2 on B1. I fixed this problem by filtering those aspiring children which can be stablized on one of the aspiring children itself. Changes made in test-prev-next.t shows the changed expected behaviour.

     1

# setup config and various utility to test new heads checks on push

     2

     3

. $TESTDIR/testlib/common.sh

     4

     5

cat >> $HGRCPATH <<EOF

     6

[ui]

     7

# simpler log output

     8

logtemplate ="{node|short} ({phase}): {desc}\n"

     9

    10

[phases]

    11

# non publishing server

    12

publish=False

    13

    14

[extensions]

    15

# we need to strip some changeset for some test cases

    16

strip=

    17

evolve=

    18

EOF

    19

    20

setuprepos() {

    21

    echo creating basic server and client repo

    22

    hg init server

    23

    cd server

    24

    mkcommit root

    25

    hg phase --public .

    26

    mkcommit A0

    27

    cd ..

    28

    hg clone server client

    29

}