From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: Barret Rhoden <brho@google.com>, Nuthan Munaiah <nm6061@rit.edu>,
git@vger.kernel.org
Subject: Re: [PATCH 3/3] blame: only coalesce lines that are adjacent in result
Date: Thu, 13 Aug 2020 11:41:57 -0700 [thread overview]
Message-ID: <xmqqv9hm1j7u.fsf@gitster.c.googlers.com> (raw)
In-Reply-To: <20200813052531.GC2514880@coredump.intra.peff.net> (Jeff King's message of "Thu, 13 Aug 2020 01:25:31 -0400")
Jeff King <peff@peff.net> writes:
> +test_expect_success 'blame does not coalesce non-adjacent result lines' '
> + cat >expect <<-EOF &&
> + $orig 1) ABC
> + $orig 3) DEF
> + EOF
> + git blame --no-abbrev -s -L1,1 -L3,3 $split giraffe >actual &&
I like this much better than "git -c core.abbrev=40", too. Good.
> + test_cmp expect actual
> +'
> +
> test_done
next prev parent reply other threads:[~2020-08-13 18:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-07 1:05 `git blame` Line Number Off-by-one Nuthan Munaiah
2020-08-07 21:21 ` Jeff King
2020-08-07 21:33 ` Jeff King
2020-08-07 21:45 ` Jeff King
2020-08-07 22:05 ` Junio C Hamano
2020-08-07 22:26 ` Jeff King
2020-08-07 22:35 ` Jeff King
2020-08-13 5:20 ` [PATCH 0/3] blame: fix bug in coalescing non-adjacent "-L" chunks Jeff King
2020-08-13 5:23 ` [PATCH 1/3] t8003: check output of coalesced blame Jeff King
2020-08-13 17:04 ` Junio C Hamano
2020-08-13 17:22 ` Jeff King
2020-08-13 5:23 ` [PATCH 2/3] t8003: factor setup out of coalesce test Jeff King
2020-08-13 5:25 ` [PATCH 3/3] blame: only coalesce lines that are adjacent in result Jeff King
2020-08-13 16:59 ` Junio C Hamano
2020-08-13 18:41 ` Junio C Hamano [this message]
2020-08-13 12:25 ` [PATCH 0/3] blame: fix bug in coalescing non-adjacent "-L" chunks Barret Rhoden
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqv9hm1j7u.fsf@gitster.c.googlers.com \
--to=gitster@pobox.com \
--cc=brho@google.com \
--cc=git@vger.kernel.org \
--cc=nm6061@rit.edu \
--cc=peff@peff.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).