path: root/merge-file.c
diff options
authorJonathan Nieder <>2010-03-21 00:40:19 (GMT)
committerJunio C Hamano <>2010-03-21 03:36:11 (GMT)
commitf0531a2937e919e763ab05e9800aef51658104fc (patch)
treedfdddc780182ea82365b37a03850d1ceadebca0d /merge-file.c
parentf01de62e4591a6acc061eb994d44f7eeef7a0cfd (diff)
checkout --conflict=diff3: add a label for ancestor
git checkout --conflict=diff3 can be used to present conflicts hunks including text from the common ancestor: <<<<<<< ours ourside ||||||| original ======= theirside >>>>>>> theirs The added information is helpful for resolving a merge by hand, and merge tools can usually understand it without trouble because it looks like output from ‘diff3 -m’. diff3 includes a label for the merge base on the ||||||| line, and it seems some tools (for example, Emacs 22’s smerge-mode) cannot parse conflict hunks without such a label. Humans could use help in interpreting the output, too. So change the marker for the start of the text from the common ancestor to include the label “base”. git rerere’s conflict identifiers are not affected: to parse conflict hunks, rerere looks for whitespace after the ||||||| marker rather than a newline, and to compute preimage ids, rerere has its own code for creating conflict hunks. No other code in git tries to parse conflict hunks. Requested-by: Stefan Monnier <> Signed-off-by: Jonathan Nieder <> Signed-off-by: Junio C Hamano <>
Diffstat (limited to 'merge-file.c')
0 files changed, 0 insertions, 0 deletions