]> git.ipfire.org Git - thirdparty/git.git/commit
t6423: expect improved conflict markers labels in the ort backend
authorElijah Newren <newren@gmail.com>
Mon, 26 Oct 2020 17:01:40 +0000 (17:01 +0000)
committerJunio C Hamano <gitster@pobox.com>
Mon, 26 Oct 2020 19:31:24 +0000 (12:31 -0700)
commitc12d1f2ac227cbec44be27de83ef07d135f243c2
treec9edc8e3ac3b9e0d11ff3132a9a9438be8ba7bc1
parent727c75b23f25f752810f412e936d420f5c7fee04
t6423: expect improved conflict markers labels in the ort backend

Conflict markers carry an extra annotation of the form
   REF-OR-COMMIT:FILENAME
to help distinguish where the content is coming from, with the :FILENAME
piece being left off if it is the same for both sides of history (thus
only renames with content conflicts carry that part of the annotation).
However, there were cases where the :FILENAME annotation was
accidentally left off, due to merge-recursive's
every-codepath-needs-a-copy-of-all-special-case-code format.

Update a few tests to have the correct :FILENAME extension on relevant
paths with the ort backend, while leaving the expectation for
merge-recursive the same to avoid destabilizing it.

Signed-off-by: Elijah Newren <newren@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
t/t6423-merge-rename-directories.sh