evolve: create a new commit instead of amending one of the divergents This patch changes the behavior of evolve command while resolving content-divergence to create a new commit instead of amending one of the divergent ones. In past, I have made this change, backed out this change and now today again I am doing this change, so let's dive in some history. Using cmdrewrite.amend() was never a good option as that requires hack to delete the evolvestate and also gives us less control over things. We can't make the commit on top of different parents as that of content-divergent ones. Due to all these, I first made this change to create a new commit instead of amending one. But, after few days, there was flakiness observed in the tests and turned out that we need to do some dirstate dance as repo.dirstate.setparents() does not always fix the dirstate. That flakiness was a blocker for progress at that time and we decided to switch to amend back so that we can have things working with some hacks and we can later fix the implementation part. Now, yesterday while tackling resolving content-divergence of a stack which is as follows: C1 C2 | | B1 B2 | | A1 A2 \/ base where, A1-A2, B1-B2, C1-C2 are content-divergent with each other. Now we can resolve A1-A2 very well because they have the same parent and let's say that resolution leads to A3. Now, we want to resolve B1-B2 and make the new resolution commit on top of A3 so that we can end up something like: C3 | B3 | A3 | base however, amending one of the divergent changesets, it's not possible to create a commit on a different parent like A3 here without some relocation. We should prevent relocation as that may leads to some conflicts and should change the parent before committing. So, looking ahead, we can't move with using amend as still using that we will need some relocation hacks making code ugly and prone to bad behaviors, bugs. Let's change back to creating a new commit so that we can move forward in a good way. About repo.dirstate.setparents() not setting the dirstate, I have researched yesterday night about how we can do that and found out that we can use cmdrewrite._uncommitdirstate() here. Expect upcoming patches to improve the documentation of that function. There are lot of test changes because of change in hash but there is no behavior change. The only behavior change is in test-evolve-abort-contentdiv.t which is nice because creating a new commit helps us in stripping that while aborting. We have a lot of testing of content-divergence and no behavior change gives enough confidence for making this change. I reviewed the patch carefully to make sure there is no behavior change and I suggest reviewer to do the same.

     1

====================================

     2

Testing head checking code: Case A-2

     3

====================================

     4

     5

Mercurial checks for the introduction of new heads on push. Evolution comes

     6

into play to detect if existing branches on the server are being replaced by

     7

some of the new one we push.

     8

     9

This case is part of a series of tests checking this behavior.

    10

    11

Category A: simple case involving a branch being superceeded by another.

    12

TestCase 2: multi-changeset branch

    13

    14

.. old-state:

    15

..

    16

.. * 1 branch with 2 changesets

    17

..

    18

.. new-state:

    19

..

    20

.. * another 2-changeset branch succeeding the old one

    21

..

    22

.. expected-result:

    23

..

    24

.. * push allowed

    25

..

    26

.. graph-summary:

    27

..

    28

..   B ø⇠◔ B'

    29

..     | |

    30

..   A ø⇠◔ A'

    31

..     |/

    32

..     ●

    33

    34

  $ . $TESTDIR/testlib/push-checkheads-util.sh

    35

    36

Test setup

    37

----------

    38

    39

  $ mkdir A2

    40

  $ cd A2

    41

  $ setuprepos

    42

  creating basic server and client repo

    43

  updating to branch default

    44

  2 files updated, 0 files merged, 0 files removed, 0 files unresolved

    45

  $ cd server

    46

  $ mkcommit B0

    47

  $ cd ../client

    48

  $ hg pull

    49

  pulling from $TESTTMP/A2/server (glob)

    50

  searching for changes

    51

  adding changesets

    52

  adding manifests

    53

  adding file changes

    54

  added 1 changesets with 1 changes to 1 files

    55

  new changesets d73caddc5533

    56

  (run 'hg update' to get a working copy)

    57

  $ hg up 0

    58

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

    59

  $ mkcommit A1

    60

  created new head

    61

  $ mkcommit B1

    62

  $ hg debugobsolete `getid "desc(A0)" ` `getid "desc(A1)"`

    63

  obsoleted 1 changesets

    64

  1 new orphan changesets

    65

  $ hg debugobsolete `getid "desc(B0)" ` `getid "desc(B1)"`

    66

  obsoleted 1 changesets

    67

  $ hg log -G --hidden

    68

  @  262c8c798096 (draft): B1

    69

  |

    70

  o  f6082bc4ffef (draft): A1

    71

  |

    72

  | x  d73caddc5533 (draft): B0

    73

  | |

    74

  | x  8aaa48160adc (draft): A0

    75

  |/

    76

  o  1e4be0697311 (public): root

    77

    78

    79

Actual testing

    80

--------------

    81

    82

  $ hg push

    83

  pushing to $TESTTMP/A2/server (glob)

    84

  searching for changes

    85

  adding changesets

    86

  adding manifests

    87

  adding file changes

    88

  added 2 changesets with 2 changes to 2 files (+1 heads)

    89

  2 new obsolescence markers

    90

  obsoleted 2 changesets

    91

    92

  $ cd ../..