All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Erik Faye-Lund <kusmabite@googlemail.com>
Cc: Matthieu Moy <Matthieu.Moy@imag.fr>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Dmitry Potapov <dpotapov@gmail.com>,
	Git Mailing List <git@vger.kernel.org>
Subject: Re: git grep '(' = segfault
Date: Mon, 27 Apr 2009 16:18:12 -0700	[thread overview]
Message-ID: <7vd4axwurv.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <40aa078e0904271202ye89ebf2wf417c623d8fe5689@mail.gmail.com> (Erik Faye-Lund's message of "Mon, 27 Apr 2009 21:02:31 +0200")

Erik Faye-Lund <kusmabite@googlemail.com> writes:

> Yeah, thanks for explaining. But isn't this functionality kind of
> redundant since we have the -E switch?
> As far as I can see, "git grep -E "(bar|boz)" should do the same thing
> as "git grep -e foo --and '(' -e bar --or -e boz ')'"...

With -E, --or is not strictly necessary.

With only -E, however, it is cumbersome to express what --and can.  Once
you learn the handiness of --and, naturally you would start wanting to
be able to say --or (especially if you do not even know about -E).

  reply	other threads:[~2009-04-27 23:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-27 17:46 git grep '(' = segfault Dmitry Potapov
2009-04-27 18:10 ` Linus Torvalds
2009-04-27 18:42   ` Erik Faye-Lund
2009-04-27 18:50     ` Linus Torvalds
2009-04-27 18:53       ` Erik Faye-Lund
2009-04-27 18:54     ` Matthieu Moy
2009-04-27 19:02       ` Erik Faye-Lund
2009-04-27 23:18         ` Junio C Hamano [this message]
2009-04-27 18:15 ` Michał Kiedrowicz

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=7vd4axwurv.fsf@gitster.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=Matthieu.Moy@imag.fr \
    --cc=dpotapov@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=kusmabite@googlemail.com \
    --cc=torvalds@linux-foundation.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 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.