From: Stefan Beller <sbeller@google.com>
To: gitster@pobox.com
Cc: git@vger.kernel.org, bmwill@google.com,
Stefan Beller <sbeller@google.com>
Subject: [PATCHv2 0/6] Add option to recurse into submodules
Date: Mon, 22 May 2017 12:48:00 -0700 [thread overview]
Message-ID: <20170522194806.13568-1-sbeller@google.com> (raw)
v2:
* this applies on sb/reset-recurse-submodules
* grep and push are also respecting submodule.recurse now.
* Brandon seemed to disagree with the first patch as it may
hurt with his 'RFC repo object' series [1], but I explained
a possible way out in [2] and Brandon seemed to agree that this
makes sense offlist.
That first patch was changed to include loading the gitmodules file
in the call to loading the config.
[1] https://public-inbox.org/git/20170518232134.163059-1-bmwill@google.com/
[2] https://public-inbox.org/git/CAGZ79kb+31h6f_9fuUpbfeY7xxjP-kbvqz6J5K5sbPEmdPNvpw@mail.gmail.com/
v1:
In a submodule heavy workflow it becomes tedious to pass in
--recurse-submodules all the time, so make an option for it.
Thanks,
Stefan
Stefan Beller (6):
submodule.c: add has_submodules to check if we have any submodules
submodule test invocation: only pass additional arguments
Introduce submodule.recurse option for worktree manipulators
builtin/fetch.c: respect 'submodule.recurse' option
builtin/grep.c: respect 'submodule.recurse' option
builtin/push.c: respect 'submodule.recurse' option
Documentation/config.txt | 5 +++
builtin/checkout.c | 9 ++--
builtin/fetch.c | 3 +-
builtin/grep.c | 3 ++
builtin/push.c | 4 ++
builtin/read-tree.c | 3 +-
builtin/reset.c | 3 +-
builtin/submodule--helper.c | 10 ++---
submodule.c | 85 +++++++++++++++++++++++++++++++-------
submodule.h | 8 +++-
t/lib-submodule-update.sh | 18 +++++++-
t/t1013-read-tree-submodule.sh | 4 +-
t/t2013-checkout-submodule.sh | 4 +-
t/t5526-fetch-submodules.sh | 10 +++++
t/t5531-deep-submodule-push.sh | 21 ++++++++++
t/t7112-reset-submodule.sh | 4 +-
t/t7814-grep-recurse-submodules.sh | 18 ++++++++
unpack-trees.c | 3 +-
18 files changed, 169 insertions(+), 46 deletions(-)
--
2.13.0.18.g7d86cc8ba0
next reply other threads:[~2017-05-22 19:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-22 19:48 Stefan Beller [this message]
2017-05-22 19:48 ` [PATCHv2 1/6] submodule.c: add has_submodules to check if we have any submodules Stefan Beller
2017-05-23 18:40 ` Brandon Williams
2017-05-23 18:52 ` Stefan Beller
2017-05-22 19:48 ` [PATCHv2 2/6] submodule test invocation: only pass additional arguments Stefan Beller
2017-05-23 6:26 ` Junio C Hamano
2017-05-23 18:29 ` Stefan Beller
2017-05-22 19:48 ` [PATCHv2 3/6] Introduce submodule.recurse option for worktree manipulators Stefan Beller
2017-05-22 19:48 ` [PATCHv2 4/6] builtin/fetch.c: respect 'submodule.recurse' option Stefan Beller
2017-05-22 19:48 ` [PATCHv2 5/6] builtin/grep.c: " Stefan Beller
2017-05-22 19:48 ` [PATCHv2 6/6] builtin/push.c: " 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=20170522194806.13568-1-sbeller@google.com \
--to=sbeller@google.com \
--cc=bmwill@google.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).