Message11542

Author jlebar
Recipients
Date 2010-01-30.03:55:59
Content
When using merge=internal:merge, merge conflicts in an hg pull --rebase are
labeled incorrectly.  The chunk local to the current repository is labeled
"other", and the chunk from the remote repository is labeled "local".

Steps to reproduce:

~$ mkdir repo1
~$ cd repo1
~/repo1$ hg init
~/repo1$ echo 'ABC' > file
~/repo1$ hg add file
~/repo1$ hg ci -m "file contains ABC"
~/repo1$ cd ..
~$ hg clone repo1 repo2
~$ cd repo2
~/repo2$ echo '111' > file
~/repo2$ hg ci -m "file contains 111"
~/repo2$ cd ../repo1
~/repo1$ echo '222' > file
~/repo1$ hg ci -m "file contains 222"
~/repo1$ cd ../repo2
~/repo2$ hg pull --rebase
pulling from /home/jlebar/repo1
searching for changes
adding changesets
adding manifests
adding file changes
added 1 changesets with 1 changes to 1 files (+1 heads)
(run 'hg heads' to see heads, 'hg merge' to merge)
merging file
warning: conflicts during merge.
merging file failed!
abort: fix unresolved conflicts with hg resolve then run hg rebase --continue

~/repo2$ cat file
<<<<<<< local
222
=======
111
>>>>>>> other
History
Date User Action Args
2010-01-30 03:55:59jlebarsetmessageid: <1264823759.57.0.452368456815.issue2007@mercurial.selenic.com>
2010-01-30 03:55:59jlebarlinkissue2007 messages
2010-01-30 03:55:59jlebarcreate