diff options
| author | Junio C Hamano <gitster@pobox.com> | 2016-04-14 22:35:09 (GMT) |
|---|---|---|
| committer | Junio C Hamano <gitster@pobox.com> | 2016-05-09 22:42:16 (GMT) |
| commit | d694a17986a28bbc19e2a6c32404ca24572e400f (patch) | |
| tree | d6fe8a53fb759e62dcb10143124ad3a695aed152 /t/t6024-recursive-merge.sh | |
| parent | ed34567c7bb1f3747255ca0301b84abad6d06712 (diff) | |
| download | git-d694a17986a28bbc19e2a6c32404ca24572e400f.zip git-d694a17986a28bbc19e2a6c32404ca24572e400f.tar.gz git-d694a17986a28bbc19e2a6c32404ca24572e400f.tar.bz2 | |
ll-merge: use a longer conflict marker for internal merge
The primary use of conflict markers is to help the user who resolves
the final (outer) merge by hand to show which part came from which
branch by separating the blocks of lines apart. When the conflicted
parts from a "virtual ancestor" merge created by merge-recursive
remains in the common ancestor part in the final result, however,
the conflict markers that are the same size as the final merge
become harder to see.
Increase the conflict marker size slightly for these inner merges so
that the markers from the final merge and cruft from internal merge
can be distinguished more easily.
This would help reduce the common issue that prevents "rerere" from
being used on a really complex conflict.
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 't/t6024-recursive-merge.sh')
| -rwxr-xr-x | t/t6024-recursive-merge.sh | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/t/t6024-recursive-merge.sh b/t/t6024-recursive-merge.sh index 755d30c..3f59e58 100755 --- a/t/t6024-recursive-merge.sh +++ b/t/t6024-recursive-merge.sh @@ -76,7 +76,7 @@ test_expect_success "result contains a conflict" "test_cmp expect a1" git ls-files --stage > out cat > expect << EOF -100644 439cc46de773d8a83c77799b7cc9191c128bfcff 1 a1 +100644 ec3fe2a791706733f2d8fa7ad45d9a9672031f5e 1 a1 100644 cf84443e49e1b366fac938711ddf4be2d4d1d9e9 2 a1 100644 fd7923529855d0b274795ae3349c5e0438333979 3 a1 EOF |