evolve: always create commit when resolving divergence When resolving content-divergence, the final commit we create may end up empty (which means that Mercurial won't even create it). We've had code for handling that in evolve ever since 41bf6c27a122 (evolve: stabilize now handle conflicting changeset, 2012-08-23). However, that resolved the issue by marking on the divergent commits as successor. As Pierre-Yves has pointed out (in other code reviews), we should instead be creating a new successor. So that's what this patch does. It does that by setting `ui.allowemptycommit` while creating the final commit. However, that is not enough, because we may end up creating the same nodeid as already existed (we'd then end up trying to mark the "new" commit a successor of itself). To solve that, we add some salt to the commit extras. That salt affects lots of tests.

     1

  $ cat >> $HGRCPATH <<EOF

     2

  > [extensions]

     3

  > EOF

     4

  $ echo "evolve=$(echo $(dirname $TESTDIR))/hgext3rd/evolve/" >> $HGRCPATH

     5

     6

Test outputting version number

     7

     8

  $ hg version -v

     9

  Mercurial Distributed SCM (version *) (glob)

    10

  (see https://mercurial-scm.org for more information)

    11

    12

  Copyright (C) 2005-* Matt Mackall and others (glob)

    13

  This is free software; see the source for copying conditions. There is NO

    14

  warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

    15

    16

  Enabled extensions:

    17

    18

    evolve  external  * (glob)

    19

    20

Test install

    21

TODO: fix warning

    22

  $ "$PYTHON" "$TESTDIR/../setup.py" install --root "$TESTTMP/installtest" > /dev/null

    23

  */distutils/dist.py:*: UserWarning: Unknown distribution option: 'python_requires' (glob)

    24

    warnings.warn(msg)