From: Noel Grandin <noel@peralex.com>
To: Trevor Saunders <tbsaunde@tbsaunde.org>,
Junio C Hamano <gitster@pobox.com>
Cc: Jeff King <peff@peff.net>, Duy Nguyen <pclouds@gmail.com>,
git <git@vger.kernel.org>
Subject: Re: feature request: excluding files/paths from "git grep"
Date: Wed, 04 Mar 2015 13:25:10 +0200 [thread overview]
Message-ID: <54F6EB96.6080500@peralex.com> (raw)
In-Reply-To: <20150302125017.GA4464@tsaunders-iceball.corp.tor1.mozilla.com>
On 2015-03-02 02:50 PM, Trevor Saunders wrote:
> I think they solve somewhat different problems, but maybe my problem is so specialized I should just have a wrapper
> around grep that changes defaults. Trev
I'm with Trevor on this one. While I see the appeal of the generality of a macro solution, this is really just about
convenience for me on a per-project basis.
As in, while working on a specific project, I sometimes just want to exclude, for the time being, a bunch of stuff from
'git grep'.
Mind you, I use 'git grep' a hang of a lot during development, since it is so powerful, so maybe that's just me.
Thanks, Noel Grandin
Disclaimer: http://www.peralex.com/disclaimer.html
next prev parent reply other threads:[~2015-03-04 11:25 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-25 12:23 feature request: excluding files/paths from "git grep" Noel Grandin
2015-02-25 13:46 ` Duy Nguyen
2015-02-25 14:31 ` Jeff King
2015-02-25 18:33 ` Junio C Hamano
2015-02-25 18:51 ` Jeff King
2015-02-25 19:01 ` Junio C Hamano
2015-02-25 19:11 ` Jeff King
2015-02-26 11:16 ` Michael J Gruber
2015-02-26 11:58 ` Duy Nguyen
2015-02-26 20:59 ` Junio C Hamano
2015-02-27 15:13 ` Michael J Gruber
2015-02-27 19:17 ` Junio C Hamano
2015-02-27 10:04 ` Trevor Saunders
2015-03-01 3:06 ` Junio C Hamano
2015-03-01 13:03 ` Trevor Saunders
2015-03-01 23:22 ` Junio C Hamano
2015-03-02 12:50 ` Trevor Saunders
2015-03-04 11:25 ` Noel Grandin [this message]
2015-03-04 20:56 ` Junio C Hamano
2015-03-05 5:22 ` Jeff King
2015-03-05 6:03 ` 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=54F6EB96.6080500@peralex.com \
--to=noel@peralex.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=pclouds@gmail.com \
--cc=peff@peff.net \
--cc=tbsaunde@tbsaunde.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.