From: Erik Faye-Lund <kusmabite@googlemail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Dmitry Potapov <dpotapov@gmail.com>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: git grep '(' = segfault
Date: Mon, 27 Apr 2009 20:42:37 +0200 [thread overview]
Message-ID: <40aa078e0904271142u71d7ba97w9df80667c0d9b955@mail.gmail.com> (raw)
In-Reply-To: <alpine.LFD.2.00.0904271059060.22156@localhost.localdomain>
On Mon, Apr 27, 2009 at 8:10 PM, Linus Torvalds
<torvalds@linux-foundation.org> wrote:
> Something like this should fix it.
>
> Linus
(Sorry that you're getting this mail twice, Linus - I forgot to reply all)
This does indeed fix the crash, but I find the resulting operation
quite bizarre. I'm getting a "fatal: unmatched paranthesis", however
"git grep '(('" is happy to simply grep for the double parenthesis.
Now, if I had done "git grep '\('", I'd expect an unmatched
parenthesis-error... Am I misunderstanding something here?
$ git grep '('
fatal: unmatched parenthesis
$ git grep '(('
Documentation/CodingGuidelines: - We use Arithmetic Expansion $(( ... )).
[...]
$ git grep '\('
fatal: command line, '\(': Unmatched ( or \(
--
Erik "kusma" Faye-Lund
kusmabite@gmail.com
(+47) 986 59 656
next prev parent reply other threads:[~2009-04-27 18:43 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 [this message]
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
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=40aa078e0904271142u71d7ba97w9df80667c0d9b955@mail.gmail.com \
--to=kusmabite@googlemail.com \
--cc=dpotapov@gmail.com \
--cc=git@vger.kernel.org \
--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 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).