From: Philip Oakley <philipoakley@iee.email>
Date: Sat, 30 May 2020 16:18:18 GMT
Subject: Re: [PATCH 0/4] Selectively show only blamed limes
Message-ID: <58ce3749-d3ef-a9fe-be94-d5373cf70f15@iee.email>
In-Reply-To: <xmqq4krz52vb.fsf@gitster.c.googlers.com>

On 28/05/2020 19:30, Junio C Hamano wrote:
> Jeff King <peff@peff.net> writes:
>
>> On Wed, May 27, 2020 at 11:24:54AM +0100, Philip Oakley wrote:
>>
>>>> I'm not convinced this is a useful thing to do in general. Lines don't
>>>> always stand on their own, and you'd lack context for deciphering them.
>>>> So a real example from "git blame -b --since=1.year.ago Makefile", for
>>>> example (pardon the long lines):
>>> My contention is that there is a lot of effort needed _beforehand_ to
>>> reach that point. We've already had to page down 2700 line to get there,
>>> and then had to carefully select the differing before and after context
>>> lines.
>> I think:
>>
>>   git blame -b --since=1.year.ago ... | less "+/^[^ ]"
>>
>> works pretty well to get you to the right spot, with context (and then
>> "/<enter>" within less takes you to the next line).
> Yup.  I think this is mostly about knowing how to use the tools that
> already exist.  I am not interested in this new "feature", either.
>
> Thanks.
Is the presumption of knowing the *nix tools something that should
documented, or is that an over simplification?

I'll trim this series to just the '^' documentation change and the '-b'
option test (after v2.27.0)

Philip