From: Stefan Beller <sbeller@google.com>
To: git@vger.kernel.org, gitster@pobox.com, jrnieder@gmail.com,
Jens.Lehmann@web.de
Cc: Stefan Beller <sbeller@google.com>
Subject: [PATCHv11 0/7] Expose submodule parallelism to the user
Date: Fri, 12 Feb 2016 15:34:33 -0800 [thread overview]
Message-ID: <1455320080-14648-1-git-send-email-sbeller@google.com> (raw)
> This replaces origin/sb/submodule-parallel-update
> and is based on origin/master
>
> * broke out the patch for redirecting errors to stderr in "submodule update"
> (Thanks Jonathan, Jacob)
> * use git_config_int and manually check for less than 0.
> (Thanks Junio)
> * use an enum consistently now for submodule update strategy
> (Thanks Junio)
> * fixed the funny indentation
* removed the indirect call to submodule_config, but made it directly
(Thanks Jonathan)
>
> I haven't looked at how this integrates with Davids refs backend, I'll take a
> look at the merge tomorrow
>
> Sorry for the long turn around time,
> Thanks,
> Stefan
Stefan Beller (7):
submodule-config: keep update strategy around
submodule-config: drop check against NULL
fetching submodules: respect `submodule.fetchJobs` config option
submodule update: direct error message to stderr
git submodule update: have a dedicated helper for cloning
submodule update: expose parallelism to the user
clone: allow an explicit argument for parallel submodule clones
Documentation/config.txt | 6 +
Documentation/git-clone.txt | 6 +-
Documentation/git-submodule.txt | 7 +-
builtin/clone.c | 19 +++-
builtin/fetch.c | 2 +-
builtin/submodule--helper.c | 239 ++++++++++++++++++++++++++++++++++++++++
git-submodule.sh | 54 ++++-----
submodule-config.c | 18 ++-
submodule-config.h | 2 +
submodule.c | 35 +++++-
submodule.h | 18 +++
t/t5526-fetch-submodules.sh | 14 +++
t/t7400-submodule-basic.sh | 4 +-
t/t7406-submodule-update.sh | 27 +++++
14 files changed, 402 insertions(+), 49 deletions(-)
--
2.7.1.292.g18a4ced.dirty
next reply other threads:[~2016-02-12 23:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-12 23:34 Stefan Beller [this message]
2016-02-12 23:34 ` [PATCHv11 1/7] submodule-config: keep update strategy around Stefan Beller
2016-02-18 19:28 ` Junio C Hamano
2016-02-12 23:34 ` [PATCHv11 2/7] submodule-config: drop check against NULL Stefan Beller
2016-02-12 23:34 ` [PATCHv11 3/7] fetching submodules: respect `submodule.fetchJobs` config option Stefan Beller
2016-02-12 23:34 ` [PATCHv11 4/7] submodule update: direct error message to stderr Stefan Beller
2016-02-12 23:34 ` [PATCHv11 5/7] git submodule update: have a dedicated helper for cloning Stefan Beller
2016-02-12 23:34 ` [PATCHv11 6/7] submodule update: expose parallelism to the user Stefan Beller
2016-02-12 23:34 ` [PATCHv11 7/7] clone: allow an explicit argument for parallel submodule clones Stefan Beller
2016-02-18 19:46 ` [PATCHv11 0/7] Expose submodule parallelism to the user 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
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=1455320080-14648-1-git-send-email-sbeller@google.com \
--to=sbeller@google.com \
--cc=Jens.Lehmann@web.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jrnieder@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.
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).