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

Test that share-clones use the cache in the original repository.

     2

     3

  $ . $TESTDIR/testlib/common.sh

     4

     5

  $ hg init share-base

     6

  $ cd share-base/

     7

  $ cat >> .hg/hgrc <<EOF

     8

  > [extensions]

     9

  > evolve=

    10

  > share=

    11

  > EOF

    12

  $ hg debugbuilddag .+3:branchpoint+4*branchpoint+2

    13

  $ cd ..

    14

  $ hg --config extensions.share= share -U share-base share-client

    15

  $ cd share-client

    16

  $ hg debugupdatecache

    17

  $ test -d .hg/cache

    18

  [1]

    19

  $ test -d ../share-base/.hg/cache

    20