From: "Daniel Heath" <daniel@heath.cc>
To: "Eric Sunshine" <sunshine@sunshineco.com>
Cc: "Git List" <git@vger.kernel.org>
Subject: Re: Bug: git log -L manpage claims regexes are supported, but they are not
Date: Fri, 04 Dec 2020 13:56:07 +1100 [thread overview]
Message-ID: <c41cbbd9-d395-41fe-9013-8a1bac68d491@www.fastmail.com> (raw)
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:
> 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
>
prev parent reply other threads:[~2020-12-04 2:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-04 2:47 Bug: git log -L manpage claims regexes are supported, but they are not Daniel
2020-12-04 2:54 ` Eric Sunshine
2020-12-04 2:56 ` Daniel Heath [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c41cbbd9-d395-41fe-9013-8a1bac68d491@www.fastmail.com \
--to=daniel@heath.cc \
--cc=git@vger.kernel.org \
--cc=sunshine@sunshineco.com \
/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.
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 NNTP newsgroup(s).