summaryrefslogtreecommitdiff
path: root/t/t4013/diff.config_format.subjectprefix_DIFFERENT_PREFIX
diff options
context:
space:
mode:
authorLibravatar Jeff King <peff@peff.net>2020-08-13 01:23:05 -0400
committerLibravatar Junio C Hamano <gitster@pobox.com>2020-08-13 10:08:10 -0700
commit6dbf0c7bebd1c71c44d786ebac0f2b3f226a0131 (patch)
treefe32c4de9a30d01173971d8412f465a8d661f3c1 /t/t4013/diff.config_format.subjectprefix_DIFFERENT_PREFIX
parentGit 2.28 (diff)
downloadtgif-6dbf0c7bebd1c71c44d786ebac0f2b3f226a0131.tar.xz
t8003: check output of coalesced blame
Commit f0cbe742f4 (blame: add a test to cover blame_coalesce(), 2019-06-20) added a test case where blame can usefully coalesce two groups of lines. But since it relies on the normal blame output, it only exercises the code and can't tell whether the lines were actually joined into a single group. However, by using --porcelain output, we can see how git-blame considers the groupings (and likewise how the coalescing might have a real user-visible impact for a tool that uses the porcelain-output groupings). This lets us confirm that we are indeed coalescing correctly (and the fact that this test case requires coalescing can be verified by dropping the call to blame_coalesce(), causing the test to fail). Signed-off-by: Jeff King <peff@peff.net> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 't/t4013/diff.config_format.subjectprefix_DIFFERENT_PREFIX')
0 files changed, 0 insertions, 0 deletions