From: Stefan Beller <sbeller@google.com>
To: Brandon Williams <bmwill@google.com>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: [PATCH 3/3] Introduce submodule.recurse option
Date: Thu, 18 May 2017 09:20:26 -0700 [thread overview]
Message-ID: <CAGZ79kZjMwoXOr_5xrU0Uy9K5bjJOd=YUBvK+Dpx+uS+5LH9Dw@mail.gmail.com> (raw)
In-Reply-To: <20170518153901.GB112091@google.com>
On Thu, May 18, 2017 at 8:39 AM, Brandon Williams <bmwill@google.com> wrote:
> On 05/17, Stefan Beller wrote:
>> Any command that understands the boolean --recurse-submodule=[true/false]
>> can have its default changed to true, by setting the submodule.recurse
>> option.
>>
>> git-push takes a --recurse-submodule argument but it is not boolean,
>> hence it is not included (yet?).
>
> ls-files and grep could also be added. They don't need to be added in
> this patch though.
I agree for git-grep.
git-ls-files is a pure plumbing command, which usually are not very accepting
of options. Then it is easier for script writers to rely on its expected output.
I just missed those two (at least grep) and will add them in this
patch if we think
this series is a good idea going forward.
Thanks,
Stefan
next prev parent reply other threads:[~2017-05-18 16:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-17 21:31 [PATCH 0/3] Add option to recurse into submodules Stefan Beller
2017-05-17 21:31 ` [PATCH 1/3] submodule.c: add has_submodules to check if we have any submodules Stefan Beller
2017-05-18 5:38 ` Junio C Hamano
2017-05-18 16:34 ` Stefan Beller
2017-05-18 15:35 ` Brandon Williams
2017-05-18 16:38 ` Stefan Beller
2017-05-18 19:00 ` Brandon Williams
2017-05-18 19:15 ` Stefan Beller
2017-05-17 21:31 ` [PATCH 2/3] submodule test invocation: only pass additional arguments Stefan Beller
2017-05-17 21:31 ` [PATCH 3/3] Introduce submodule.recurse option Stefan Beller
2017-05-18 15:39 ` Brandon Williams
2017-05-18 16:20 ` Stefan Beller [this message]
2017-05-18 19:05 ` [PATCH 0/3] Add option to recurse into submodules Brandon Williams
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='CAGZ79kZjMwoXOr_5xrU0Uy9K5bjJOd=YUBvK+Dpx+uS+5LH9Dw@mail.gmail.com' \
--to=sbeller@google.com \
--cc=bmwill@google.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.
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).