Re: Bug: git log -L manpage claims regexes are supported, but they are not

From: Daniel Heath <daniel@heath.cc>
Date: Dec 4, 2020, 02:56 UTC
Message-ID: <c41cbbd9-d395-41fe-9013-8a1bac68d491@www.fastmail.com>
In-Reply-To: <CAPig+cT-Tf2ray+j9b45vz-qoiSZ4MkTyGVDr6PRJCXsvbx0=Q@mail.gmail.com>

Thanks very much!

I was thrown by `git blame` having an almost-identical but opposite interface (must use a space and not a colon).

Thanks, Daniel Heath

On Fri, Dec 4, 2020, at 1:54 PM, Eric Sunshine wrote:

Show 12 quoted lines

> On Thu, Dec 3, 2020 at 9:50 PM Daniel <daniel@heath.cc> wrote:
> >    $ git log -L ^/bootstrap-sass/,+2 Gemfile
> > fatal: -L argument not 'start,end:file' or ':funcname:file':
> > ^/bootstrap-sass/,+2
> >
> > $ git help log
> >         -L <start>,<end>:<file>, -L :<funcname>:<file>
> 
> You're missing the colon between <end> and <file> in your example. It should be:
> 
>     $ git log -L ^/bootstrap-sass/,+2:Gemfile
>