From: Stefan Beller <sbeller@google.com>
To: bmwill@google.com
Cc: git@vger.kernel.org, gitster@pobox.com,
Stefan Beller <sbeller@google.com>
Subject: [PATCHv2 0/8] A reroll of sb/submodule-blanket-recursive
Date: Fri, 26 May 2017 12:10:09 -0700 [thread overview]
Message-ID: <20170526191017.19155-1-sbeller@google.com> (raw)
v2:
* A reroll of sb/submodule-blanket-recursive.
* This requires ab/grep-preparatory-cleanup
* It changed a lot from v1, as in v1 the tests did not work,
hence the code was broken. Now it actually works.
* it also includes grep, fetch, push in addition to plain working tree
manipulators.
Thanks,
Stefan
Stefan Beller (8):
submodule recursing: do not write a config variable twice
submodule test invocation: only pass additional arguments
reset/checkout/read-tree: unify config callback for submodule
recursion
submodule loading: separate code path for .gitmodules and config
overlay
Introduce 'submodule.recurse' option for worktree manipulators
builtin/grep.c: respect 'submodule.recurse' option
builtin/push.c: respect 'submodule.recurse' option
builtin/fetch.c: respect 'submodule.recurse' option
Documentation/config.txt | 5 +++
builtin/checkout.c | 31 ++----------------
builtin/fetch.c | 7 +++++
builtin/grep.c | 3 ++
builtin/push.c | 4 +++
builtin/read-tree.c | 32 ++++++-------------
builtin/reset.c | 39 +++++++----------------
submodule.c | 64 +++++++++++++++++++++++++++++++++-----
submodule.h | 7 ++++-
t/lib-submodule-update.sh | 22 ++++++++++---
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 +++++++++++
16 files changed, 178 insertions(+), 97 deletions(-)
--
2.13.0.17.g582985b1e4
next reply other threads:[~2017-05-26 19:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-26 19:10 Stefan Beller [this message]
2017-05-26 19:10 ` [PATCH 1/8] submodule recursing: do not write a config variable twice Stefan Beller
2017-05-26 19:10 ` [PATCH 2/8] submodule test invocation: only pass additional arguments Stefan Beller
2017-05-26 19:10 ` [PATCH 3/8] reset/checkout/read-tree: unify config callback for submodule recursion Stefan Beller
2017-05-26 19:10 ` [PATCH 4/8] submodule loading: separate code path for .gitmodules and config overlay Stefan Beller
2017-05-26 19:10 ` [PATCH 5/8] Introduce 'submodule.recurse' option for worktree manipulators Stefan Beller
2017-05-26 19:10 ` [PATCH 6/8] builtin/grep.c: respect 'submodule.recurse' option Stefan Beller
2017-05-26 19:10 ` [PATCH 7/8] builtin/push.c: " Stefan Beller
2017-05-26 19:10 ` [PATCH 8/8] builtin/fetch.c: " Stefan Beller
2017-05-30 5:30 ` [PATCHv2 0/8] A reroll of sb/submodule-blanket-recursive Junio C Hamano
2017-06-01 0:30 ` [PATCHv3 0/4] " Stefan Beller
2017-06-01 0:30 ` [PATCHv3 1/4] Introduce 'submodule.recurse' option for worktree manipulators Stefan Beller
2017-06-01 0:30 ` [PATCHv3 2/4] builtin/grep.c: respect 'submodule.recurse' option Stefan Beller
2017-06-01 0:30 ` [PATCHv3 3/4] builtin/push.c: " Stefan Beller
2017-06-01 0:30 ` [PATCHv3 4/4] builtin/fetch.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=20170526191017.19155-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).