From: Linus Torvalds <torvalds@osdl.org>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] builtin-grep: workaround for non GNU grep.
Date: Wed, 17 May 2006 12:42:53 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0605171239420.10823@g5.osdl.org> (raw)
In-Reply-To: <7vodxwcwa1.fsf@assigned-by-dhcp.cox.net>
On Wed, 17 May 2006, Junio C Hamano wrote:
>
> This makes -c misbehave in a subtle way.
>
> git grep -c -e no-such-string-anywhere | head -n 1
>
> But I do not think we care.
Ahh, yes. That appears to be unfixable without using special GNU
extensions.
I agree that we probably don't care, though.
Linus
next prev parent reply other threads:[~2006-05-17 19:43 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-16 23:52 Git 1.3.2 on Solaris Stefan Pfetzing
2006-05-17 1:25 ` Jason Riedy
2006-05-17 2:20 ` Linus Torvalds
2006-05-17 3:26 ` Jason Riedy
2006-05-17 3:49 ` Linus Torvalds
2006-05-17 8:05 ` Stefan Pfetzing
2006-05-17 14:33 ` Linus Torvalds
2006-05-17 15:08 ` Stefan Pfetzing
2006-05-17 16:24 ` Linus Torvalds
2006-05-17 16:35 ` Jason Riedy
2006-05-23 3:20 ` Stefan Pfetzing
2006-05-23 4:51 ` Jason Riedy
2006-05-23 12:04 ` Stefan Pfetzing
2006-05-23 14:53 ` Linus Torvalds
2006-05-23 15:20 ` Edgar Toernig
2006-05-23 15:31 ` Linus Torvalds
2006-05-23 18:43 ` Edgar Toernig
2006-05-23 18:03 ` Jason Riedy
2006-05-23 18:24 ` Linus Torvalds
2006-05-23 18:48 ` Linus Torvalds
2006-05-26 3:30 ` Stefan Pfetzing
2006-05-17 5:15 ` Ryan Anderson
2006-05-17 8:22 ` Junio C Hamano
2006-05-17 9:03 ` Junio C Hamano
2006-05-17 9:54 ` [PATCH] builtin-grep: workaround for non GNU grep Junio C Hamano
2006-05-17 14:24 ` Linus Torvalds
2006-05-17 17:41 ` Junio C Hamano
2006-05-17 15:39 ` Bertrand Jacquin
2006-05-17 17:42 ` Junio C Hamano
2006-05-17 18:12 ` Linus Torvalds
2006-05-17 18:59 ` Junio C Hamano
2006-05-17 19:42 ` Linus Torvalds [this message]
2006-05-17 8:28 ` Git 1.3.2 on Solaris Junio C Hamano
2006-05-17 9:06 ` Stefan Pfetzing
2006-05-17 9:22 ` Junio C Hamano
2006-05-17 10:41 ` Stefan Pfetzing
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=Pine.LNX.4.64.0605171239420.10823@g5.osdl.org \
--to=torvalds@osdl.org \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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).