| commit | 6054d1aac36d5769461fb73b15326a900e53edb9 | |
| author | Elijah Newren <newren@gmail.com> | |
| Wed, 2 Feb 2022 02:37:33 +0000 (2 02:37 +0000) | ||
| committer | Junio C Hamano <gitster@pobox.com> | |
| Wed, 2 Feb 2022 18:02:27 +0000 (2 10:02 -0800) | ||
| tree | f013c7245bdb44814a3a56de132413f46fa12724 | treesnapshot (tar.gz zip) |
| parent | a28d094ac276da2f6dd8132355baaedf685342ef | commitdiff |
merge-ort: format messages slightly different for use in headers
When users run
git show --remerge-diff $MERGE_COMMIT
or
git log -p --remerge-diff ...
stdout is not an appropriate location to dump conflict messages, but we
do want to provide them to users. We will include them in the diff
headers instead...but for that to work, we need for any multiline
messages to replace newlines with both a newline and a space. Add a new
flag to signal when we want these messages modified in such a fashion,
and use it in path_msg() to modify these messages this way. Also, allow
a special prefix to be specified for these headers.
Signed-off-by: Elijah Newren <newren@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
When users run
git show --remerge-diff $MERGE_COMMIT
or
git log -p --remerge-diff ...
stdout is not an appropriate location to dump conflict messages, but we
do want to provide them to users. We will include them in the diff
headers instead...but for that to work, we need for any multiline
messages to replace newlines with both a newline and a space. Add a new
flag to signal when we want these messages modified in such a fashion,
and use it in path_msg() to modify these messages this way. Also, allow
a special prefix to be specified for these headers.
Signed-off-by: Elijah Newren <newren@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
| merge-ort.c | diffblobblamehistory | |
| merge-recursive.c | diffblobblamehistory | |
| merge-recursive.h | diffblobblamehistory |