From: Stefan Beller <sbeller@google.com>
To: sbeller@google.com, git@vger.kernel.org, gitster@pobox.com
Cc: jrnieder@gmail.com, Jens.Lehmann@web.de
Subject: [PATCHv7 0/8] Expose submodule parallelism to the user
Date: Mon, 11 Jan 2016 11:41:53 -0800 [thread overview]
Message-ID: <1452541321-27810-1-git-send-email-sbeller@google.com> (raw)
This is a resend of sb/submodule-parallel-update and is available at github[1] as well.
It applies on top of sb/submodule-parallel-fetch
What does it do?
---
This series should finish the on going efforts of parallelizing
submodule network traffic. The patches contain tests for
clone
fetch
submodule update
to use the actual parallelism both via command line as well as a
configured option. I decided to go with "submodule.fetchJobs" for
all three for now.
What changed to v5,6?
---
No major changes, I just made it compile again as the order of parameters
to the parallel processing engine changed.
Thanks,
Stefan
[1] https://github.com/stefanbeller/git/tree/submodule-parallel-update-v7
Stefan Beller (8):
submodule-config: keep update strategy around
submodule-config: drop check against NULL
submodule-config: remove name_and_item_from_var
submodule-config: introduce parse_generic_submodule_config
fetching submodules: respect `submodule.fetchJobs` config option
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 | 7 ++
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 | 109 +++++++++++-------
submodule-config.h | 3 +
submodule.c | 5 +
t/t5526-fetch-submodules.sh | 14 +++
t/t7400-submodule-basic.sh | 4 +-
t/t7406-submodule-update.sh | 27 +++++
13 files changed, 413 insertions(+), 83 deletions(-)
--
2.7.0.rc1.7.gf4541cb.dirty
next reply other threads:[~2016-01-11 19:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-11 19:41 Stefan Beller [this message]
2016-01-11 19:41 ` [PATCHv7 1/8] submodule-config: keep update strategy around Stefan Beller
2016-01-11 19:41 ` [PATCHv7 2/8] submodule-config: drop check against NULL Stefan Beller
2016-01-11 19:41 ` [PATCHv7 3/8] submodule-config: remove name_and_item_from_var Stefan Beller
2016-01-11 19:41 ` [PATCHv7 4/8] submodule-config: introduce parse_generic_submodule_config Stefan Beller
2016-01-11 19:41 ` [PATCHv7 5/8] fetching submodules: respect `submodule.fetchJobs` config option Stefan Beller
2016-01-11 19:41 ` [PATCHv7 6/8] git submodule update: have a dedicated helper for cloning Stefan Beller
2016-01-11 19:42 ` [PATCHv7 7/8] submodule update: expose parallelism to the user Stefan Beller
2016-01-11 19:42 ` [PATCHv7 8/8] clone: allow an explicit argument for parallel submodule clones Stefan Beller
2016-01-12 23:50 ` [PATCHv7 0/8] Expose submodule parallelism to the user Junio C Hamano
2016-01-12 23:59 ` Stefan Beller
2016-01-13 16:56 ` Junio C Hamano
2016-01-13 17:48 ` Stefan Beller
2016-01-20 20:53 ` Junio C Hamano
-- strict thread matches above, loose matches on Subject: below --
2016-02-02 17:51 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=1452541321-27810-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).