diff options
author | Thomas Gummerer <t.gummerer@gmail.com> | 2018-08-28 23:27:44 +0200 |
---|---|---|
committer | Junio C Hamano <gitster@pobox.com> | 2018-08-29 18:03:29 +0200 |
commit | f427869bde759e32c30e8ba7a4b20837d3806642 (patch) | |
tree | be2af8c44ed90d7bb7c94e2e5f3478fa05bc2e62 | |
parent | rerere: mention caveat about unmatched conflict markers (diff) | |
download | git-f427869bde759e32c30e8ba7a4b20837d3806642.tar.xz git-f427869bde759e32c30e8ba7a4b20837d3806642.zip |
rerere: add note about files with existing conflict markers
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 <gitster@pobox.com>
Signed-off-by: Thomas Gummerer <t.gummerer@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
-rw-r--r-- | Documentation/git-rerere.txt | 6 |
1 files changed, 6 insertions, 0 deletions
diff --git a/Documentation/git-rerere.txt b/Documentation/git-rerere.txt index 031f31fa47..df310d2a58 100644 --- a/Documentation/git-rerere.txt +++ b/Documentation/git-rerere.txt @@ -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 |