From: Michael J Gruber <git@drmicha.warpmail.net>
To: Nguyen Thai Ngoc Duy <pclouds@gmail.com>
Cc: Phil Hord <hordp@cisco.com>,
David Chanters <david.chanters@googlemail.com>,
git@vger.kernel.org
Subject: Re: git-grep to operate across who repository and not just CWD?
Date: Tue, 01 Mar 2011 09:54:55 +0100 [thread overview]
Message-ID: <4D6CB45F.1030800@drmicha.warpmail.net> (raw)
In-Reply-To: <AANLkTim78nQgS7NPXWErQyrqmt41OUXY6gzJmMwjtxo9@mail.gmail.com>
Nguyen Thai Ngoc Duy venit, vidit, dixit 01.03.2011 09:16:
> On Tue, Mar 1, 2011 at 3:05 PM, Michael J Gruber
> <git@drmicha.warpmail.net> wrote:
>> I would love "git grep" to be repowise, with the simple "git grep ." to
>> make it relative to cwd. We've discussed making more commands repowise,
>> and the consensus (which I've stated above, accepting the majority vote)
>> was that some should stay, e.g. git-grep. The discussion started with
>>
>> <http://permalink.gmane.org/gmane.comp.version-control.git/166135>
>>
>> and the consensus is stated here:
>>
>> <http://permalink.gmane.org/gmane.comp.version-control.git/167149>
>>
>> This does not prevent you from submitting a "--full-tree" patch for
>> git-grep, of course.
>
> In fact Junio wrote one:
>
> http://mid.gmane.org/7vk4xggv27.fsf@alter.siamese.dyndns.org
Oh yes, thanks for reminding me. And guess who replied first back then?
Oh well...
> If I remember correctly, it was dropped because of the interaction
> with pathspecs (relative to cwd vs to worktree's root). I'd be great
> if someone can pick it up and finish it.
Rereading that thread, I don't think there was any objection against
"--full-tree", but it suffered from DTD (discussed-to-death). To make it
really usefull, one would need a short-cut/option/whatever, and that's
where the discussion went astray. I have an idea, though :)
Michael
next prev parent reply other threads:[~2011-03-01 8:58 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-28 0:17 git-grep to operate across who repository and not just CWD? David Chanters
2011-02-28 9:27 ` Michael J Gruber
2011-02-28 15:27 ` Jay Soffian
2011-02-28 18:32 ` Junio C Hamano
2011-02-28 18:38 ` Junio C Hamano
2011-02-28 22:25 ` Phil Hord
2011-03-01 8:05 ` Michael J Gruber
2011-03-01 8:16 ` Nguyen Thai Ngoc Duy
2011-03-01 8:54 ` Michael J Gruber [this message]
2011-03-01 9:32 ` Nguyen Thai Ngoc Duy
2011-03-01 9:44 ` Nguyen Thai Ngoc Duy
2011-03-01 9:53 ` [PATCH/POC 0/2] grep --full-tree Michael J Gruber
2011-03-01 9:53 ` [PATCH/RFC 1/2] grep: --full-tree Michael J Gruber
2011-03-01 9:53 ` [PATCH/RFC 2/2] grep: make --full-tree work with pathspecs Michael J Gruber
2011-03-01 19:20 ` Junio C Hamano
2011-03-01 10:21 ` [PATCH/alternative/raw and rough] setup.c: denote repo wide pathspecs by ':' Michael J Gruber
2011-03-01 11:13 ` Nguyen Thai Ngoc Duy
2011-03-01 11:16 ` Michael J Gruber
2011-03-01 11:50 ` Nguyen Thai Ngoc Duy
2011-03-01 11:57 ` Michael J Gruber
2011-03-01 12:08 ` Nguyen Thai Ngoc Duy
2011-03-01 14:50 ` Junio C Hamano
2011-03-01 15:01 ` Michael J Gruber
2011-03-01 20:00 ` Junio C Hamano
2011-03-02 12:34 ` Sverre Rabbelier
2011-03-02 12:57 ` Nguyen Thai Ngoc Duy
2011-03-02 13:12 ` Michael J Gruber
2011-03-02 16:53 ` Junio C Hamano
2011-03-02 17:31 ` Michael J Gruber
2011-03-03 2:42 ` Miles Bader
2011-03-03 3:52 ` Junio C Hamano
2011-03-03 3:44 ` Phil Hord
2011-03-03 8:20 ` Michael J Gruber
2011-03-01 16:25 ` Phil Hord
2011-03-01 18:31 ` James Pickens
2011-03-02 0:12 ` Nguyen Thai Ngoc Duy
2011-03-03 3:51 ` Phil Hord
2011-03-03 8:21 ` Michael J Gruber
2011-03-01 11:49 ` Michael J Gruber
2011-03-01 13:05 ` Phil Hord
2011-03-23 15:32 ` [PATCH] pathspec: reserve some letters after a colon pathspec Nguyễn Thái Ngọc Duy
2011-03-23 18:04 ` Junio C Hamano
2011-03-24 7:15 ` Michael J Gruber
2011-03-24 7:49 ` Nguyen Thai Ngoc Duy
2011-03-24 8:12 ` Junio C Hamano
2011-03-24 14:46 ` 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=4D6CB45F.1030800@drmicha.warpmail.net \
--to=git@drmicha.warpmail.net \
--cc=david.chanters@googlemail.com \
--cc=git@vger.kernel.org \
--cc=hordp@cisco.com \
--cc=pclouds@gmail.com \
/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).