From: Mischa POSLAWSKY <git@shiar.nl>
To: Junio C Hamano <gitster@pobox.com>
Cc: "Stefan Beller" <sbeller@google.com>,
"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
git <git@vger.kernel.org>,
myon@debian.org
Subject: Re: [PATCH] grep: provide a noop --recursive option
Date: Fri, 5 Oct 2018 15:05:16 +0200 [thread overview]
Message-ID: <20181005130516.3qnhtjg7js53iomf@shiar.net> (raw)
In-Reply-To: <xmqqftxkztzb.fsf@gitster-ct.c.googlers.com>
Junio C Hamano wrote 2018-10-05 1:19 (-0700):
> Stefan Beller <sbeller@google.com> writes:
>
> > git-grep is always file/tree recursive, but there is --recurse-submodules
> > which is off by default. Instead of providing a short alias to a noop,
> > we could use -r for submodules. (And if you happen to have no
> > submodules, this is a noop for you)
>
> I am not sure if it is an overall win for those who do have and use
> submodules to easily be able to go recursive with a short-and-sweet
> 'r', or even they want to work inside one project at a time most of
> the time. If the latter, then using 'r' for recurse-submodules is
> going to be a mistake (besides, other commands that have 'recursive'
> typically use 'r' for its shorthand,and 'r' does not stand for
> 'recurse-submodules' for them).
Personally I would welcome a shorthand for --recurse-submodules,
especially if --r^I no longer completes to this.
It is also closer to the behaviour provided by grep -r as that recurses
into submodules as well.
Regards,
--
Mischa
next prev parent reply other threads:[~2018-10-05 13:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-29 14:01 wishlist: git grep -r Christoph Berg
2018-09-29 14:55 ` [PATCH] grep: provide a noop --recursive option Ævar Arnfjörð Bjarmason
2018-09-29 15:08 ` Duy Nguyen
2018-09-29 15:25 ` Ævar Arnfjörð Bjarmason
2018-09-29 15:47 ` Duy Nguyen
2018-09-29 17:11 ` Junio C Hamano
2018-09-29 19:38 ` Christoph Berg
2018-10-01 19:15 ` René Scharfe
2018-10-05 8:17 ` Junio C Hamano
2018-10-05 12:49 ` Ævar Arnfjörð Bjarmason
2018-10-01 19:23 ` Stefan Beller
2018-10-05 8:15 ` Christoph Berg
2018-10-05 8:19 ` Junio C Hamano
2018-10-05 13:05 ` Mischa POSLAWSKY [this message]
2018-10-05 19:17 ` Stefan Beller
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20181005130516.3qnhtjg7js53iomf@shiar.net \
--to=git@shiar.nl \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=myon@debian.org \
--cc=sbeller@google.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).