comparison tests/test-merge9.out @ 5045:f191bc3916f7

merge: do early copy to deal with issue636 Without copies/renames, merges source names are 1:1 with their targets. Copies and renames introduce the possibility that there will be two merges with the same input but different output. By doing the copy to the destination name before the merge, the actual merge becomes 1:1 again, and no source is the input to two different merges. - add a preliminary scan to applyupdates to do copies - for the merge action, pass the old name (for finding ancestors) and the new name (for input to the merge) to filemerge - eliminate the old post-merge copy - lookup file contents from new name in filemerge - pass new name to external merge helper - report merge failure at new name - add a test
author Matt Mackall <mpm@selenic.com>
date Wed, 01 Aug 2007 12:33:12 -0500
parents dc5920ea12f8
children
comparison
equal deleted inserted replaced
5029:ac97e065cfc7 5045:f191bc3916f7
3 adding quux1 3 adding quux1
4 adding quux2 4 adding quux2
5 merging bar 5 merging bar
6 merging bar failed! 6 merging bar failed!
7 merging foo and baz 7 merging foo and baz
8 merging foo failed! 8 merging baz failed!
9 1 files updated, 0 files merged, 0 files removed, 2 files unresolved 9 1 files updated, 0 files merged, 0 files removed, 2 files unresolved
10 There are unresolved merges, you can redo the full merge using: 10 There are unresolved merges, you can redo the full merge using:
11 hg update -C 2 11 hg update -C 2
12 hg merge 1 12 hg merge 1
13 3 files updated, 0 files merged, 1 files removed, 0 files unresolved 13 3 files updated, 0 files merged, 1 files removed, 0 files unresolved