From: Ingo Molnar <mingo@elte.hu>
To: Miklos Vajna <vmiklos@frugalware.org>
Cc: "René Scharfe" <rene.scharfe@lsrfire.ath.cx>, git@vger.kernel.org
Subject: Re: git-grep: small suggestion, -w flag
Date: Sun, 22 Feb 2009 18:23:00 +0100 [thread overview]
Message-ID: <20090222172300.GF6570@elte.hu> (raw)
In-Reply-To: <20090222172055.GW4371@genesis.frugalware.org>
* Miklos Vajna <vmiklos@frugalware.org> wrote:
> On Sun, Feb 22, 2009 at 05:14:10PM +0100, Ingo Molnar <mingo@elte.hu> wrote:
> > earth4:~/tip> git grep -lw schedule
> > usage: git grep <option>* [-e] <pattern> <rev>* [[--] <path>...]
> >
> >
> > should have been 'git grep -l -w schedule'.
>
> Yeah, that's because git-grep does not use parseopt yet.
>
> I'm willing to work on it once mv/parseopt-ls-files is settled
> down.
As long as it's planned eventually i'm a happy camper! No rush.
Ingo
prev parent reply other threads:[~2009-02-22 17:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-22 10:34 git-grep: small suggestion, -w flag Ingo Molnar
2009-02-22 11:15 ` René Scharfe
2009-02-22 16:14 ` Ingo Molnar
2009-02-22 17:20 ` Miklos Vajna
2009-02-22 17:23 ` Ingo Molnar [this message]
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=20090222172300.GF6570@elte.hu \
--to=mingo@elte.hu \
--cc=git@vger.kernel.org \
--cc=rene.scharfe@lsrfire.ath.cx \
--cc=vmiklos@frugalware.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).