Skip to content

Commit

Permalink
rerere: add note about files with existing conflict markers
Browse files Browse the repository at this point in the history
When a file contains lines that look like conflict markers, 'git
rerere' may fail not be able to record a conflict resolution.
Emphasize that in the man page, and mention a possible workaround for
the issue.

Suggested-by: Junio C Hamano <[email protected]>
Signed-off-by: Thomas Gummerer <[email protected]>
Signed-off-by: Junio C Hamano <[email protected]>
  • Loading branch information
tgummerer authored and gitster committed Aug 29, 2018
1 parent bc4caec commit f427869
Showing 1 changed file with 6 additions and 0 deletions.
6 changes: 6 additions & 0 deletions Documentation/git-rerere.txt
Original file line number Diff line number Diff line change
Expand Up @@ -211,6 +211,12 @@ would conflict the same way as the test merge you resolved earlier.
'git rerere' will be run by 'git rebase' to help you resolve this
conflict.

[NOTE] 'git rerere' relies on the conflict markers in the file to
detect the conflict. If the file already contains lines that look the
same as lines with conflict markers, 'git rerere' may fail to record a
conflict resolution. To work around this, the `conflict-marker-size`
setting in linkgit:gitattributes[5] can be used.

GIT
---
Part of the linkgit:git[1] suite

0 comments on commit f427869

Please sign in to comment.