From: "孙世龙 sunshilong" <sunshilong369@gmail.com>
To: Carlo Arenas <carenas@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: How can I search git log with ceratin keyword but without the other keyword?
Date: Sat, 11 Jul 2020 13:48:04 +0800 [thread overview]
Message-ID: <CAAvDm6avvkXrU-Q8zu7C5WFqfCbf0DN=6cPMU-rOxgmdAh1Ebw@mail.gmail.com> (raw)
In-Reply-To: <CAPUEspg=4HJL8iiNrNp9Wr9sVj5Gw_PciSezHV5iJ1w-ymdzdw@mail.gmail.com>
Thank you for taking the time to respond to me.
When I run the said shell command, this error reported:
# git log -P --all-match --grep '12' --grep '\b(?!t123\b)\w+'
fatal: unrecognized argument: -P
The version of git which I am currently using is 2.7.4.
One more question, could you please explain '\b(?!t123\b)\w+' in
more detail for me?
Or suggest some related documents for me to go through?
Thank you for your help.
Best regards.
On Fri, Jul 10, 2020 at 4:14 PM Carlo Arenas <carenas@gmail.com> wrote:
>
> it is easier to write specific "not match" using PCRE syntax, but
> there are several other options to choose from combining as many
> expressions as needed from the `git log` man page:
>
> git log -P --all-match --grep '12' --grep '\b(?!t123\b)\w+'
>
> Carlo
next prev parent reply other threads:[~2020-07-11 5:48 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-10 4:31 How can I search git log with ceratin keyword but without the other keyword? 孙世龙 sunshilong
2020-07-10 8:14 ` Carlo Arenas
2020-07-11 5:48 ` 孙世龙 sunshilong [this message]
2020-07-16 15:31 ` Jeff King
2020-07-17 1:45 ` 孙世龙 sunshilong
2020-07-17 6:33 ` Jeff King
2020-07-17 7:45 ` Junio C Hamano
2020-07-17 10:19 ` Junio C Hamano
2020-07-18 4:51 ` 孙世龙 sunshilong
2020-07-18 18:07 ` Junio C Hamano
2020-07-19 5:28 ` 孙世龙 sunshilong
2020-07-19 8:26 ` Carlo Arenas
2020-07-20 17:50 ` Junio C Hamano
2020-07-22 6:46 ` Carlo Arenas
2020-07-17 10:27 ` 孙世龙 sunshilong
2020-07-17 10:42 ` 孙世龙 sunshilong
[not found] <BYAPR21MB11587632058438090FE265B8E0DA9@BYAPR21MB1158.namprd21.prod.outlook.com>
2020-12-27 23:45 ` Dan Moseley
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='CAAvDm6avvkXrU-Q8zu7C5WFqfCbf0DN=6cPMU-rOxgmdAh1Ebw@mail.gmail.com' \
--to=sunshilong369@gmail.com \
--cc=carenas@gmail.com \
--cc=git@vger.kernel.org \
/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).