sapling/tests/test-backout.t

718 lines
15 KiB
Perl
Raw Normal View History

$ . helpers-usechg.sh
2010-08-14 04:28:53 +04:00
$ hg init basic
$ cd basic
should complain
2010-08-14 04:28:53 +04:00
$ hg backout
abort: please specify a revision to backout
2010-09-17 02:51:32 +04:00
[255]
2010-08-14 04:28:53 +04:00
$ hg backout -r 0 0
abort: please specify just one revision
2010-09-17 02:51:32 +04:00
[255]
2010-08-14 04:28:53 +04:00
basic operation
(this also tests that editor is invoked if the commit message is not
specified explicitly)
(this also tests correctness of default message)
2010-08-14 04:28:53 +04:00
$ echo a > a
$ hg commit -d '0 0' -A -m a
adding a
$ echo b >> a
$ hg commit -d '1 0' -m $'b\nc'
2010-08-14 04:28:53 +04:00
$ hg status --rev tip --rev "tip^1"
M a
$ HGEDITOR=cat hg backout -d '2 0' tip --tool=true
2010-08-14 04:28:53 +04:00
reverting a
Back out "b"
Original commit changeset: a451c20d3c0b
HG: Enter commit message. Lines beginning with 'HG:' are removed.
HG: Leave message empty to abort commit.
HG: --
HG: user: test
HG: branch 'default'
HG: changed a
changeset 2:8540552e2ce9 backs out changeset 1:a451c20d3c0b
2010-08-14 04:28:53 +04:00
$ cat a
a
$ hg summary
parent: 2:8540552e2ce9 tip
Back out "b"
commit: (clean)
phases: 3 draft
2010-08-14 04:28:53 +04:00
commit option
$ cd ..
$ hg init commit
$ cd commit
$ echo tomatoes > a
$ hg add a
$ hg commit -d '0 0' -m tomatoes
$ echo chair > b
$ hg add b
$ hg commit -d '1 0' -m chair
$ echo grapes >> a
$ hg commit -d '2 0' -m grapes
$ hg backout -d '4 0' 1 --tool=:fail
0 files updated, 0 files merged, 1 files removed, 0 files unresolved
changeset 3:6b2e5750efab backs out changeset 1:22cb4f70d813
$ hg summary
parent: 3:6b2e5750efab tip
Back out "chair"
commit: (clean)
phases: 4 draft
$ echo ypples > a
$ hg commit -d '5 0' -m ypples
$ hg backout -d '6 0' 2 --tool=:fail
0 files updated, 0 files merged, 0 files removed, 1 files unresolved
use 'hg resolve' to retry unresolved file merges
[1]
$ hg summary
parent: 4:2cf19744f63f tip
ypples
commit: 1 unresolved (clean)
phases: 5 draft
file that was removed is recreated
(this also tests that editor is not invoked if the commit message is
specified explicitly)
2010-08-14 04:28:53 +04:00
$ cd ..
$ hg init remove
$ cd remove
$ echo content > a
$ hg commit -d '0 0' -A -m a
adding a
$ hg rm a
$ hg commit -d '1 0' -m b
$ HGEDITOR=cat hg backout -d '2 0' tip --tool=true -m "Backed out changeset 76862dcce372"
2010-08-14 04:28:53 +04:00
adding a
changeset 2:0ab3c2be0b32 backs out changeset 1:76862dcce372
2010-08-14 04:28:53 +04:00
$ cat a
content
$ hg summary
parent: 2:0ab3c2be0b32 tip
Backed out changeset 76862dcce372
commit: (clean)
phases: 3 draft
2010-08-14 04:28:53 +04:00
backout of backout is as if nothing happened
2010-08-14 04:28:53 +04:00
$ hg backout -d '3 0' --merge tip --tool=true
2010-08-14 04:28:53 +04:00
removing a
changeset 3:5b1b9b2a0f35 backs out changeset 2:0ab3c2be0b32
$ test -f a
[1]
$ hg summary
parent: 3:5b1b9b2a0f35 tip
Back out "Backed out changeset 76862dcce372"
commit: (clean)
phases: 4 draft
2010-08-14 04:28:53 +04:00
2015-07-30 00:16:12 +03:00
Test that 'hg rollback' restores dirstate just before opening
transaction: in-memory dirstate changes should be written into
'.hg/journal.dirstate' as expected.
$ echo 'removed soon' > b
$ hg commit -A -d '4 0' -m 'prepare for subsequent removing'
adding b
$ echo 'newly added' > c
$ hg add c
$ hg remove b
$ hg commit -d '5 0' -m 'prepare for subsequent backout'
$ touch -t 200001010000 c
$ hg status -A
C c
$ hg debugstate --nodates
n 644 12 set c
$ hg backout -d '6 0' -m 'to be rollback-ed soon' -r .
adding b
removing c
changeset 6:3ab761ce0df4 backs out changeset 5:19a306f2a2e0
2015-07-30 00:16:12 +03:00
$ hg rollback -q
$ hg status -A
A b
R c
$ hg debugstate --nodates
a 0 -1 unset b
r 0 0 unset c
2015-07-30 00:16:12 +03:00
across branch
2010-08-14 04:28:53 +04:00
$ cd ..
$ hg init branch
$ cd branch
$ echo a > a
$ hg ci -Am0
adding a
$ echo b > b
$ hg ci -Am1
adding b
$ hg co -C 0
0 files updated, 0 files merged, 1 files removed, 0 files unresolved
$ hg summary
parent: 0:f7b1eb17ad24
0
commit: (clean)
phases: 2 draft
2010-08-14 04:28:53 +04:00
should fail
$ hg backout 1
abort: cannot backout change that is not an ancestor
2010-09-17 02:51:32 +04:00
[255]
2010-08-14 04:28:53 +04:00
$ echo c > c
$ hg ci -Am2
adding c
$ hg summary
parent: 2:db815d6d32e6 tip
2
commit: (clean)
phases: 3 draft
2010-08-14 04:28:53 +04:00
should fail
$ hg backout 1
abort: cannot backout change that is not an ancestor
2010-09-17 02:51:32 +04:00
[255]
$ hg summary
parent: 2:db815d6d32e6 tip
2
commit: (clean)
phases: 3 draft
2010-08-14 04:28:53 +04:00
backout with merge
2010-08-14 04:28:53 +04:00
$ cd ..
$ hg init merge
$ cd merge
$ echo line 1 > a
$ echo line 2 >> a
$ hg commit -d '0 0' -A -m a
adding a
$ hg summary
parent: 0:59395513a13a tip
a
commit: (clean)
phases: 1 draft
2010-08-14 04:28:53 +04:00
remove line 1
$ echo line 2 > a
$ hg commit -d '1 0' -m b
$ echo line 3 >> a
$ hg commit -d '2 0' -m c
$ hg backout --merge -d '3 0' 1 --tool=true
2010-08-14 04:28:53 +04:00
reverting a
changeset 3:d3729c426fdb backs out changeset 1:5a50a024c182
merging with changeset 3:d3729c426fdb
2010-08-14 04:28:53 +04:00
merging a
0 files updated, 1 files merged, 0 files removed, 0 files unresolved
(branch merge, don't forget to commit)
$ hg commit -d '4 0' -m d
$ hg summary
parent: 4:76e753f52d24 tip
d
commit: (clean)
phases: 5 draft
2010-08-14 04:28:53 +04:00
check line 1 is back
$ cat a
line 1
line 2
line 3
Test visibility of in-memory dirstate changes outside transaction to
external hook process
$ cat > $TESTTMP/checkvisibility.sh <<EOF
> echo "==== \$1:"
> hg parents --template "{rev}:{node|short}\n"
> echo "===="
> EOF
"hg backout --merge REV1" at REV2 below implies steps below:
(1) update to REV1 (REV2 => REV1)
(2) revert by REV1^1
(3) commit backing out revision (REV3)
(4) update to REV2 (REV3 => REV2)
(5) merge with REV3 (REV2 => REV2, REV3)
== test visibility to external preupdate hook
$ hg update -q -C 2
$ hg --config extensions.strip= strip 3
saved backup bundle to * (glob)
$ cat >> .hg/hgrc <<EOF
> [hooks]
> preupdate.visibility = sh $TESTTMP/checkvisibility.sh preupdate
> EOF
("-m" is needed to avoid writing dirstate changes out at other than
invocation of the hook to be examined)
$ hg backout --merge -d '3 0' 1 --tool=true -m 'fixed comment'
==== preupdate:
2:6ea3f2a197a2
====
reverting a
changeset 3:9a3b8b6c2523 backs out changeset 1:5a50a024c182
==== preupdate:
3:9a3b8b6c2523
====
merging with changeset 3:9a3b8b6c2523
==== preupdate:
2:6ea3f2a197a2
====
merging a
0 files updated, 1 files merged, 0 files removed, 0 files unresolved
(branch merge, don't forget to commit)
$ cat >> .hg/hgrc <<EOF
> [hooks]
> preupdate.visibility =
> EOF
merge: make in-memory changes visible to external update hooks c67339617276 (while 3.4 code-freeze) made all 'update' hooks run after releasing wlock for visibility of in-memory dirstate changes. But this breaks paired invocation of 'preupdate' and 'update' hooks. For example, 'hg backout --merge' for TARGET revision, which isn't parent of CURRENT, consists of steps below: 1. update from CURRENT to TARGET 2. commit BACKOUT revision, which backs TARGET out 3. update from BACKOUT to CURRENT 4. merge TARGET into CURRENT Then, we expects hooks to run in the order below: - 'preupdate' on CURRENT for (1) - 'update' on TARGET for (1) - 'preupdate' on BACKOUT for (3) - 'update' on CURRENT for (3) - 'preupdate' on TARGET for (4) - 'update' on CURRENT/TARGET for (4) But hooks actually run in the order below: - 'preupdate' on CURRENT for (1) - 'preupdate' on BACKOUT for (3) - 'preupdate' on TARGET for (4) - 'update' on TARGET for (1), but actually on CURRENT/TARGET - 'update' on CURRENT for (3), but actually on CURRENT/TARGET - 'update' on CURRENT for (4), but actually on CURRENT/TARGET Root cause of the issue focused by c67339617276 is that external 'update' hook process can't view in-memory changes (especially, of dirstate), because they aren't written out until the end of transaction (or wlock). Now, hooks can be invoked just after updating, because previous patches made in-memory changes visible to external process. This patch may break backward compatibility from the point of view of "scheduling hook execution", but should be reasonable because 'update' hooks had been executed in this order before 3.4. This patch tests "hg backout" and "hg unshelve", because the former activates the transaction before 'update' hook invocation, but the former doesn't.
2015-10-16 19:15:34 +03:00
== test visibility to external update hook
$ hg update -q -C 2
$ hg --config extensions.strip= strip 3
saved backup bundle to * (glob)
$ cat >> .hg/hgrc <<EOF
> [hooks]
> update.visibility = sh $TESTTMP/checkvisibility.sh update
> EOF
$ hg backout --merge -d '3 0' 1 --tool=true -m 'fixed comment'
==== update:
1:5a50a024c182
====
reverting a
changeset 3:9a3b8b6c2523 backs out changeset 1:5a50a024c182
merge: make in-memory changes visible to external update hooks c67339617276 (while 3.4 code-freeze) made all 'update' hooks run after releasing wlock for visibility of in-memory dirstate changes. But this breaks paired invocation of 'preupdate' and 'update' hooks. For example, 'hg backout --merge' for TARGET revision, which isn't parent of CURRENT, consists of steps below: 1. update from CURRENT to TARGET 2. commit BACKOUT revision, which backs TARGET out 3. update from BACKOUT to CURRENT 4. merge TARGET into CURRENT Then, we expects hooks to run in the order below: - 'preupdate' on CURRENT for (1) - 'update' on TARGET for (1) - 'preupdate' on BACKOUT for (3) - 'update' on CURRENT for (3) - 'preupdate' on TARGET for (4) - 'update' on CURRENT/TARGET for (4) But hooks actually run in the order below: - 'preupdate' on CURRENT for (1) - 'preupdate' on BACKOUT for (3) - 'preupdate' on TARGET for (4) - 'update' on TARGET for (1), but actually on CURRENT/TARGET - 'update' on CURRENT for (3), but actually on CURRENT/TARGET - 'update' on CURRENT for (4), but actually on CURRENT/TARGET Root cause of the issue focused by c67339617276 is that external 'update' hook process can't view in-memory changes (especially, of dirstate), because they aren't written out until the end of transaction (or wlock). Now, hooks can be invoked just after updating, because previous patches made in-memory changes visible to external process. This patch may break backward compatibility from the point of view of "scheduling hook execution", but should be reasonable because 'update' hooks had been executed in this order before 3.4. This patch tests "hg backout" and "hg unshelve", because the former activates the transaction before 'update' hook invocation, but the former doesn't.
2015-10-16 19:15:34 +03:00
==== update:
2:6ea3f2a197a2
====
merging with changeset 3:9a3b8b6c2523
merge: make in-memory changes visible to external update hooks c67339617276 (while 3.4 code-freeze) made all 'update' hooks run after releasing wlock for visibility of in-memory dirstate changes. But this breaks paired invocation of 'preupdate' and 'update' hooks. For example, 'hg backout --merge' for TARGET revision, which isn't parent of CURRENT, consists of steps below: 1. update from CURRENT to TARGET 2. commit BACKOUT revision, which backs TARGET out 3. update from BACKOUT to CURRENT 4. merge TARGET into CURRENT Then, we expects hooks to run in the order below: - 'preupdate' on CURRENT for (1) - 'update' on TARGET for (1) - 'preupdate' on BACKOUT for (3) - 'update' on CURRENT for (3) - 'preupdate' on TARGET for (4) - 'update' on CURRENT/TARGET for (4) But hooks actually run in the order below: - 'preupdate' on CURRENT for (1) - 'preupdate' on BACKOUT for (3) - 'preupdate' on TARGET for (4) - 'update' on TARGET for (1), but actually on CURRENT/TARGET - 'update' on CURRENT for (3), but actually on CURRENT/TARGET - 'update' on CURRENT for (4), but actually on CURRENT/TARGET Root cause of the issue focused by c67339617276 is that external 'update' hook process can't view in-memory changes (especially, of dirstate), because they aren't written out until the end of transaction (or wlock). Now, hooks can be invoked just after updating, because previous patches made in-memory changes visible to external process. This patch may break backward compatibility from the point of view of "scheduling hook execution", but should be reasonable because 'update' hooks had been executed in this order before 3.4. This patch tests "hg backout" and "hg unshelve", because the former activates the transaction before 'update' hook invocation, but the former doesn't.
2015-10-16 19:15:34 +03:00
merging a
==== update:
2:6ea3f2a197a2
3:9a3b8b6c2523
merge: make in-memory changes visible to external update hooks c67339617276 (while 3.4 code-freeze) made all 'update' hooks run after releasing wlock for visibility of in-memory dirstate changes. But this breaks paired invocation of 'preupdate' and 'update' hooks. For example, 'hg backout --merge' for TARGET revision, which isn't parent of CURRENT, consists of steps below: 1. update from CURRENT to TARGET 2. commit BACKOUT revision, which backs TARGET out 3. update from BACKOUT to CURRENT 4. merge TARGET into CURRENT Then, we expects hooks to run in the order below: - 'preupdate' on CURRENT for (1) - 'update' on TARGET for (1) - 'preupdate' on BACKOUT for (3) - 'update' on CURRENT for (3) - 'preupdate' on TARGET for (4) - 'update' on CURRENT/TARGET for (4) But hooks actually run in the order below: - 'preupdate' on CURRENT for (1) - 'preupdate' on BACKOUT for (3) - 'preupdate' on TARGET for (4) - 'update' on TARGET for (1), but actually on CURRENT/TARGET - 'update' on CURRENT for (3), but actually on CURRENT/TARGET - 'update' on CURRENT for (4), but actually on CURRENT/TARGET Root cause of the issue focused by c67339617276 is that external 'update' hook process can't view in-memory changes (especially, of dirstate), because they aren't written out until the end of transaction (or wlock). Now, hooks can be invoked just after updating, because previous patches made in-memory changes visible to external process. This patch may break backward compatibility from the point of view of "scheduling hook execution", but should be reasonable because 'update' hooks had been executed in this order before 3.4. This patch tests "hg backout" and "hg unshelve", because the former activates the transaction before 'update' hook invocation, but the former doesn't.
2015-10-16 19:15:34 +03:00
====
0 files updated, 1 files merged, 0 files removed, 0 files unresolved
(branch merge, don't forget to commit)
$ cat >> .hg/hgrc <<EOF
> [hooks]
> update.visibility =
> EOF
$ cd ..
backout should not back out subsequent changesets
2010-08-14 04:28:53 +04:00
$ hg init onecs
$ cd onecs
$ echo 1 > a
$ hg commit -d '0 0' -A -m a
adding a
$ echo 2 >> a
$ hg commit -d '1 0' -m b
$ echo 1 > b
$ hg commit -d '2 0' -A -m c
adding b
$ hg summary
parent: 2:882396649954 tip
c
commit: (clean)
phases: 3 draft
without --merge
$ hg backout --no-commit -d '3 0' 1 --tool=true
1 files updated, 0 files merged, 0 files removed, 0 files unresolved
changeset 22bca4c721e5 backed out, don't forget to commit.
$ hg locate b
b
$ hg update -C tip
1 files updated, 0 files merged, 0 files removed, 0 files unresolved
$ hg locate b
b
$ hg summary
parent: 2:882396649954 tip
c
commit: (clean)
phases: 3 draft
with --merge
$ hg backout --merge -d '3 0' 1 --tool=true
reverting a
changeset 3:19e57856498e backs out changeset 1:22bca4c721e5
merging with changeset 3:19e57856498e
1 files updated, 0 files merged, 0 files removed, 0 files unresolved
(branch merge, don't forget to commit)
2010-08-14 04:28:53 +04:00
$ hg locate b
b
$ hg update -C tip
1 files updated, 0 files merged, 1 files removed, 0 files unresolved
$ hg locate b
2010-09-17 02:51:32 +04:00
[1]
2010-08-14 04:28:53 +04:00
$ cd ..
$ hg init m
$ cd m
$ echo a > a
$ hg commit -d '0 0' -A -m a
adding a
$ echo b > b
$ hg commit -d '1 0' -A -m b
adding b
$ echo c > c
$ hg commit -d '2 0' -A -m b
adding c
$ hg update 1
0 files updated, 0 files merged, 1 files removed, 0 files unresolved
$ echo d > d
$ hg commit -d '3 0' -A -m c
adding d
$ hg merge 2
1 files updated, 0 files merged, 0 files removed, 0 files unresolved
(branch merge, don't forget to commit)
$ hg commit -d '4 0' -A -m d
$ hg summary
parent: 4:b2f3bb92043e tip
d
commit: (clean)
phases: 5 draft
2010-08-14 04:28:53 +04:00
backout of merge should fail
2010-08-14 04:28:53 +04:00
$ hg backout 4
abort: cannot backout a merge changeset
2010-09-17 02:51:32 +04:00
[255]
2010-08-14 04:28:53 +04:00
backout of merge with bad parent should fail
2010-08-14 04:28:53 +04:00
$ hg backout --parent 0 4
abort: cb9a9f314b8b is not a parent of b2f3bb92043e
2010-09-17 02:51:32 +04:00
[255]
2010-08-14 04:28:53 +04:00
backout of non-merge with parent should fail
2010-08-14 04:28:53 +04:00
$ hg backout --parent 0 3
abort: cannot use --parent on non-merge changeset
2010-09-17 02:51:32 +04:00
[255]
2010-08-14 04:28:53 +04:00
backout with valid parent should be ok
2010-08-14 04:28:53 +04:00
$ hg backout -d '5 0' --parent 2 4 --tool=true
2010-08-14 04:28:53 +04:00
removing d
changeset 5:84e16af81ce4 backs out changeset 4:b2f3bb92043e
$ hg summary
parent: 5:84e16af81ce4 tip
Back out "d"
commit: (clean)
phases: 6 draft
2010-08-14 04:28:53 +04:00
$ hg rollback
repository tip rolled back to revision 4 (undo commit)
working directory now based on revision 4
2010-08-14 04:28:53 +04:00
$ hg update -C
1 files updated, 0 files merged, 0 files removed, 0 files unresolved
$ hg summary
parent: 4:b2f3bb92043e tip
d
commit: (clean)
phases: 5 draft
2010-08-14 04:28:53 +04:00
$ hg backout -d '6 0' --parent 3 4 --tool=true
2010-08-14 04:28:53 +04:00
removing c
changeset 5:042ecc423244 backs out changeset 4:b2f3bb92043e
$ hg summary
parent: 5:042ecc423244 tip
Back out "d"
commit: (clean)
phases: 6 draft
2010-08-14 04:28:53 +04:00
$ cd ..
named branches
2010-08-14 04:28:53 +04:00
$ hg init named_branches
$ cd named_branches
$ echo default > default
$ hg ci -d '0 0' -Am default
adding default
$ hg branch branch1
marked working directory as branch branch1
2011-12-09 00:32:44 +04:00
(branches are permanent and global, did you want a bookmark?)
2010-08-14 04:28:53 +04:00
$ echo branch1 > file1
$ hg ci -d '1 0' -Am file1
adding file1
$ hg branch branch2
marked working directory as branch branch2
$ echo branch2 > file2
$ hg ci -d '2 0' -Am file2
adding file2
without --merge
$ hg backout --no-commit -r 1 --tool=true
0 files updated, 0 files merged, 1 files removed, 0 files unresolved
changeset bf1602f437f3 backed out, don't forget to commit.
$ hg branch
branch2
$ hg status -A
R file1
C default
C file2
$ hg summary
parent: 2:45bbcd363bf0 tip
file2
commit: 1 removed
phases: 3 draft
with --merge
(this also tests that editor is invoked if '--edit' is specified
explicitly regardless of '--message')
$ hg update -qC
$ HGEDITOR=cat hg backout --merge -d '3 0' -r 1 -m 'backout on branch1' --tool=true --edit
2010-08-14 04:28:53 +04:00
removing file1
backout on branch1
Original commit changeset: bf1602f437f3
HG: Enter commit message. Lines beginning with 'HG:' are removed.
HG: Leave message empty to abort commit.
HG: --
HG: user: test
HG: branch 'branch2'
HG: removed file1
changeset 3:8857f307d2b3 backs out changeset 1:bf1602f437f3
merging with changeset 3:8857f307d2b3
0 files updated, 0 files merged, 1 files removed, 0 files unresolved
(branch merge, don't forget to commit)
$ hg summary
parent: 2:45bbcd363bf0
file2
parent: 3:8857f307d2b3 tip
backout on branch1
commit: 1 removed (merge)
phases: 4 draft
$ hg update -q -C 2
2010-08-14 04:28:53 +04:00
on branch2 with branch1 not merged, so file1 should still exist:
$ hg id
45bbcd363bf0 (branch2)
$ hg st -A
C default
C file1
C file2
$ hg summary
parent: 2:45bbcd363bf0
file2
commit: (clean)
phases: 4 draft
2010-08-14 04:28:53 +04:00
on branch2 with branch1 merged, so file1 should be gone:
$ hg merge
0 files updated, 0 files merged, 1 files removed, 0 files unresolved
(branch merge, don't forget to commit)
$ hg ci -d '4 0' -m 'merge backout of branch1'
$ hg id
6b63d6afbede (branch2) tip
2010-08-14 04:28:53 +04:00
$ hg st -A
C default
C file2
$ hg summary
parent: 4:6b63d6afbede tip
merge backout of branch1
commit: (clean)
phases: 5 draft
2010-08-14 04:28:53 +04:00
on branch1, so no file1 and file2:
$ hg co -C branch1
1 files updated, 0 files merged, 1 files removed, 0 files unresolved
$ hg id
bf1602f437f3 (branch1)
$ hg st -A
C default
C file1
$ hg summary
parent: 1:bf1602f437f3
file1
commit: (clean)
phases: 5 draft
$ cd ..
backout of empty changeset (issue4190)
$ hg init emptycommit
$ cd emptycommit
$ touch file1
$ hg ci -Aqm file1
$ hg branch -q branch1
$ hg ci -qm branch1
$ hg backout -v 1
resolving manifests
nothing changed
[1]
$ cd ..
Test usage of `hg resolve` in case of conflict
(issue4163)
$ hg init issue4163
$ cd issue4163
$ touch foo
$ hg add foo
$ cat > foo << EOF
> one
> two
> three
> four
> five
> six
> seven
> height
> nine
> ten
> EOF
$ hg ci -m 'initial'
$ cat > foo << EOF
> one
> two
> THREE
> four
> five
> six
> seven
> height
> nine
> ten
> EOF
$ hg ci -m 'capital three'
$ cat > foo << EOF
> one
> two
> THREE
> four
> five
> six
> seven
> height
> nine
> TEN
> EOF
$ hg ci -m 'capital ten'
$ hg backout -r 'desc("capital three")' --tool internal:fail
0 files updated, 0 files merged, 0 files removed, 1 files unresolved
use 'hg resolve' to retry unresolved file merges
[1]
$ hg status
$ hg debugmergestate
* version 2 records
local: b71750c4b0fdf719734971e3ef90dbeab5919a2d
other: a30dd8addae3ce71b8667868478542bc417439e6
file extras: foo (ancestorlinknode = 91360952243723bd5b1138d5f26bd8c8564cb553)
file: foo (record type "F", state "u", hash 0beec7b5ea3f0fdbc95d0dd47f3c5bc275da8a33)
local path: foo (flags "")
ancestor path: foo (node f89532f44c247a0e993d63e3a734dd781ab04708)
other path: foo (node f50039b486d6fa1a90ae51778388cad161f425ee)
$ mv .hg/merge/state2 .hg/merge/state2-moved
$ hg debugmergestate
* version 1 records
local: b71750c4b0fdf719734971e3ef90dbeab5919a2d
file: foo (record type "F", state "u", hash 0beec7b5ea3f0fdbc95d0dd47f3c5bc275da8a33)
local path: foo (flags "")
ancestor path: foo (node f89532f44c247a0e993d63e3a734dd781ab04708)
other path: foo (node not stored in v1 format)
$ mv .hg/merge/state2-moved .hg/merge/state2
$ hg resolve -l # still unresolved
U foo
$ hg summary
parent: 2:b71750c4b0fd tip
capital ten
commit: 1 unresolved (clean)
phases: 3 draft
$ hg resolve --all --debug
picked tool ':merge' for foo (binary False symlink False changedelete False)
merging foo
my foo@b71750c4b0fd+ other foo@a30dd8addae3 ancestor foo@913609522437
premerge successful
(no more unresolved files)
continue: hg commit
$ hg status
M foo
? foo.orig
$ hg resolve -l
R foo
$ hg summary
parent: 2:b71750c4b0fd tip
capital ten
commit: 1 modified, 1 unknown
phases: 3 draft
$ cat foo
one
two
three
four
five
six
seven
height
nine
TEN
--no-commit shouldn't commit
$ hg init a
$ cd a
$ for i in 1 2 3; do
> touch $i
> hg ci -Am $i
> done
adding 1
adding 2
adding 3
$ hg backout --no-commit .
removing 3
changeset cccc23d9d68f backed out, don't forget to commit.
$ hg revert -aq
--no-commit can't be used with --merge
$ hg backout --merge --no-commit 2
abort: cannot use --merge with --no-commit
[255]