From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: [PATCH] built-in "git grep" (git grip).
Date: Tue, 02 May 2006 11:25:10 +0200 [thread overview]
Message-ID: <e378fs$lpc$1@sea.gmane.org> (raw)
In-Reply-To: 7vy7xkn6kd.fsf@assigned-by-dhcp.cox.net
Junio C Hamano wrote:
> Andreas Ericsson <ae@op5.se> writes:
>
>> "git grip" work just fine for me, since it's only intended for testing
>> and performance improvements so far. I also think it's clearer for
>> end-users looking for a grep command if they're not faced with
>> fgrep/egrep/ggrep/bgrep alongside plain "grep".
>
> I renamed "git grip" to "git grep" and "git diffn" to "git diff"
> both in "next" branch to avoid confusion. Thanks Andreas,
> Jakub, and others for input.
So, is there a way to use old, script version of those commands?
--
Jakub Narebski
Warsaw, Poland
next prev parent reply other threads:[~2006-05-02 9:24 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-01 6:32 [PATCH] built-in "git grep" (git grip) Junio C Hamano
2006-05-01 6:56 ` Jakub Narebski
2006-05-01 6:59 ` Junio C Hamano
2006-05-01 7:12 ` Jakub Narebski
2006-05-02 8:33 ` Andreas Ericsson
2006-05-02 8:44 ` Jakub Narebski
2006-05-02 9:01 ` Junio C Hamano
2006-05-02 9:25 ` Jakub Narebski [this message]
2006-05-02 9:39 ` Andreas Ericsson
2006-05-02 19:07 ` Junio C Hamano
2006-05-02 21:23 ` Linus Torvalds
2006-05-02 21:54 ` Junio C Hamano
2006-05-02 23:07 ` Linus Torvalds
2006-05-03 0:01 ` Junio C Hamano
2006-05-01 7:30 ` [PATCH] built-in "git grep" (git grip) - quickfix Junio C Hamano
2006-05-01 14:04 ` [PATCH] built-in "git grep" (git grip) Sam Ravnborg
2006-05-01 14:07 ` Sam Ravnborg
2006-05-01 14:53 ` Sam Ravnborg
2006-05-01 15:48 ` Linus Torvalds
2006-05-01 19:30 ` [PATCH] builtin-grep: wildcard pathspec fixes Junio C Hamano
2006-05-01 23:24 ` [PATCH] builtin-grep: do not use setup_revisions() Junio C Hamano
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='e378fs$lpc$1@sea.gmane.org' \
--to=jnareb@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).