| commit | b9b07efdb2ac35684d3ee3fe98f91691d5b8642a | |
| author | Thomas Gummerer <t.gummerer@gmail.com> | |
| Tue, 28 Aug 2018 22:05:50 +0000 (28 23:05 +0100) | ||
| committer | Junio C Hamano <gitster@pobox.com> | |
| Wed, 29 Aug 2018 18:27:31 +0000 (29 11:27 -0700) | ||
| tree | ca2a6d7e8f5c5f17098c9a2c4f4b5adcb464d1bd | treesnapshot (tar.gz zip) |
| parent | 53f9a3e157dbbc901a02ac2c73346d375e24978c | commitdiff |
.gitattributes: add conflict-marker-size for relevant files
Some files in git.git contain lines that look like conflict markers,
either in examples or tests, or in the case of Documentation/gitk.txt
because of the asciidoc heading.
Having conflict markers the same length as the actual content can be
confusing for humans, and is impossible to handle for tools like 'git
rerere'. Work around that by setting the 'conflict-marker-size'
attribute for those files to 32, which makes the conflict markers
unambiguous.
Helped-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>
Some files in git.git contain lines that look like conflict markers,
either in examples or tests, or in the case of Documentation/gitk.txt
because of the asciidoc heading.
Having conflict markers the same length as the actual content can be
confusing for humans, and is impossible to handle for tools like 'git
rerere'. Work around that by setting the 'conflict-marker-size'
attribute for those files to 32, which makes the conflict markers
unambiguous.
Helped-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>
| .gitattributes | diffblobblamehistory |