From: Junio C Hamano <gitster@pobox.com>
To: "孙世龙 sunshilong" <sunshilong369@gmail.com>
Cc: Jeff King <peff@peff.net>, Carlo Arenas <carenas@gmail.com>,
git@vger.kernel.org
Subject: Re: How can I search git log with ceratin keyword but without the other keyword?
Date: Sat, 18 Jul 2020 11:07:54 -0700 [thread overview]
Message-ID: <xmqqlfjgbssl.fsf@gitster.c.googlers.com> (raw)
In-Reply-To: <CAAvDm6bG-s2m9fGXVtuyLB7_FSDRduhb3ptrBsL3ezR9LaS-hQ@mail.gmail.com> ("孙世龙 sunshilong"'s message of "Sat, 18 Jul 2020 12:51:53 +0800")
孙世龙 sunshilong <sunshilong369@gmail.com> writes:
> Thank you for your detailed explanation.
>
>>There is not much room for the line-level "--not" operator to
>>participate in this picture.
> After I have carefully read your explanation again and again.
> Maybe, I think there is a way to achieve this goal.
> Please point out if there is something wrong.
Sorry, it is currently not in the area of interest for me to examine
an extensive rewrite of the "grep" machinery for unknown benefit.
The cost-benefit ratio does not look too great to just add "X && !Y"
support to existing "X && Y" logic. If we were seriously extending
the machinery, I'd rather see us shooting for even more generic
boolean expression support, not just "our --all-match currently
requires all of the AND-ed terms to positively match, but lets make
it possible to require some of these terms not to fire at all".
next prev parent reply other threads:[~2020-07-18 18:07 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
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 [this message]
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=xmqqlfjgbssl.fsf@gitster.c.googlers.com \
--to=gitster@pobox.com \
--cc=carenas@gmail.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
--cc=sunshilong369@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.