git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[PATCH 0/3] expose parallelism for submodule {update, clone}

From
Stefan Beller <sbeller@google.com>
Date
Oct 23, 2015, 18:44 UTC
Message-ID
<1445625879-30330-1-git-send-email-sbeller@google.com>

This goes on top of origin/sb/submodule-parallel-fetch^ The first patch replaces the last patch of origin/sb/submodule-parallel-fetch using clearer names for the callback functions.

The patches 2 and 3 introduce CLI options for {submodule update, clone} to instruct Git to be parallel for cloning submodule operations.

Additionally `git submodule update` respects the config option "submodule.jobs".

I also want to make "git fetch --recurse-submodules" and "git clone --recursive" respect the same "submodule.jobs" config option, but that code change would collide with origin/sb/submodule-config-parse, so I will put the patches on top of that.

Stefan Beller (3):
  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/git-clone.txt     |   5 +-
 Documentation/git-submodule.txt |   6 +-
 builtin/clone.c                 |  23 ++--
 builtin/submodule--helper.c     | 234 ++++++++++++++++++++++++++++++++++++++++
 git-submodule.sh                |  54 ++++------
 t/t7400-submodule-basic.sh      |   4 +-
 6 files changed, 282 insertions(+), 44 deletions(-)
-- 
2.6.2.280.g74301d6
Next: Stefan Beller
Message 1 of 7 in “expose parallelism for submodule {update, clone}”
  1. 0/3 expose parallelism for submodule {update, clone}Stefan Beller, Oct 23, 2015
  2. 1/3 git submodule update: have a dedicated helper for cloningStefan Beller, Oct 23, 2015
  3. 2/3 submodule update: Expose parallelism to the userStefan Beller, Oct 23, 2015
  4. 3/3 clone: Allow an explicit argument for parallel submodule clonesStefan Beller, Oct 23, 2015
  5. Sebastian SchuberthOct 28, 2015
  6. Junio C HamanoOct 23, 2015
  7. Stefan BellerOct 23, 2015

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.