Re: [PATCH 2/2] Documentation/git-log: mention that line-log regex must match in starting revision

From: Philippe Blain <levraiphilippeblain@gmail.com>
Date: Dec 18, 2019, 03:28 UTC
Message-ID: <147443E8-EA04-45D2-B3BC-D879A5FFECDC@gmail.com>
In-Reply-To: <xmqq5zieizrb.fsf@gitster-ct.c.googlers.com>

Show 5 quoted lines

> Le 17 déc. 2019 à 13:16, Junio C Hamano <gitster@pobox.com> a écrit :
> Even when you specify <start> or <end> as a line number, they must
> exist in the starting revision or it would be a fatal error.  If we
> are clarifying with this patch for completeness, I think we should
> also mention it together.

Thanks for the feedback. I did some tests : 
    git log -L 73,2000000085:Documentation/git-log.txt
does not error and shows the history from line 73 to the end of the file.
    git log -L 300,2000000085:Documentation/git-log.txt 
errors out:
    fatal: file Documentation/git-log.txt has only 239 lines
But 
    git log -L 300,-2000000085:Documentation/git-log.txt
does not error out and shows the history for the whole file. Also,
    git log -L 1,-2000000085:Documentation/git-log.txt
does not error out and gives the history for the first line.

So I think that it’s really only regex that must match...