##// END OF EJS Templates
commit: when committing the results of a merge, it's all or nothing...
commit: when committing the results of a merge, it's all or nothing Previously, it was possible to commit just one file from a merge, which is essentially always the wrong thing to do. This fixes issue 1049.

File last commit:

r5210:90d9ec0d default
r6385:0d4e068e default
Show More
test-issue522
31 lines | 677 B | text/plain | TextLexer
Alexis S. L. Carvalho
merge: forcefully mark files that we get from the second parent as dirty...
r5210 #!/bin/sh
# In the merge below, the file "foo" has the same contents in both
# parents, but if we look at the file-level history, we'll notice that
# the version in p1 is an ancestor of the version in p2. This test
# makes sure that we'll use the version from p2 in the manifest of the
# merge revision.
hg init repo
cd repo
echo foo > foo
hg ci -d '0 0' -qAm 'add foo'
echo bar >> foo
hg ci -d '0 0' -m 'change foo'
hg backout -d '0 0' -r tip -m 'backout changed foo'
hg up -C 0
touch bar
hg ci -d '0 0' -qAm 'add bar'
hg merge --debug
hg debugstate | grep foo
hg st -A foo
hg ci -d '0 0' -m 'merge'
hg manifest --debug | grep foo
hg debugindex .hg/store/data/foo.i