summaryrefslogtreecommitdiff
path: root/Documentation/git-request-pull.txt
diff options
context:
space:
mode:
authorLibravatar Elijah Newren <newren@gmail.com>2022-02-02 02:37:36 +0000
committerLibravatar Junio C Hamano <gitster@pobox.com>2022-02-02 10:02:28 -0800
commit0d83d8240ddb3f54da44563b73527dbc50c4ed22 (patch)
tree7d526d3d68f583d8f38d037606fee6fcb7660e79 /Documentation/git-request-pull.txt
parentshow, log: include conflict/warning messages in --remerge-diff headers (diff)
downloadtgif-0d83d8240ddb3f54da44563b73527dbc50c4ed22.tar.xz
merge-ort: mark conflict/warning messages from inner merges as omittable
A recursive merge involves merging the merge bases of the two branches being merged. Such an inner merge can itself generate conflict notices. While such notices may be useful when initially trying to create a merge, they seem to just be noise when investigating merges later with --remerge-diff. (Especially when both sides of the outer merge resolved the conflict the same way leading to no overall conflict.) Remove them. Signed-off-by: Elijah Newren <newren@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'Documentation/git-request-pull.txt')
0 files changed, 0 insertions, 0 deletions