comparison tests/test-evolve-content-divergent-first-changeset.t @ 4984:b779b40f996e stable

evolve: fix content-divergence resolution when p1 is null (issue6201) Before this fix, in cases like in the added test, the revision number -1 of the parent was misinterpreted to mean the tipmost revision instead of the null revision, causing the content-divergence resolution to fail.
author Manuel Jacob <me@manueljacob.de>
date Fri, 06 Dec 2019 14:01:29 +0100
parents
children 1f92a6aa40d6 946ebd8f08ea
comparison
equal deleted inserted replaced
4981:60be1bd580c7 4984:b779b40f996e
1 $ . $TESTDIR/testlib/pythonpath.sh
2 $ echo "[extensions]" >> $HGRCPATH
3 $ echo "evolve=" >> $HGRCPATH
4
5 This test file tests the case of content-divergence resolution of changesets
6 that have the null revision as the parent.
7
8 $ hg init issue6201
9 $ cd issue6201
10
11 $ touch test
12 $ hg add test
13 $ hg commit -m test
14 $ hg log -T '{node|short}\n'
15 be090ea66256
16
17 $ echo a >> test
18 $ hg amend -m div1
19 $ hg log -T '{node|short}\n'
20 79fa0eb22d65
21
22 $ hg up be090ea66256 --hidden --quiet
23 updated to hidden changeset be090ea66256
24 (hidden revision 'be090ea66256' was rewritten as: 79fa0eb22d65)
25 working directory parent is obsolete! (be090ea66256)
26 $ echo a >> test
27 $ echo b >> test
28 $ hg amend -m div2
29 2 new content-divergent changesets
30 $ hg log -T '{node|short}\n'
31 4b2524b7508e
32 79fa0eb22d65
33
34 $ hg evolve --content-divergent --config ui.merge=internal:other
35 merge:[1] div1
36 with: [2] div2
37 base: [0] test
38 0 files updated, 1 files merged, 0 files removed, 0 files unresolved
39 working directory is now at 12772224141b
40
41 $ hg evolve --list