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

[PATCH 0/1] fetch --multiple: respect --jobs=

From
Johannes Schindelin via GitGitGadget <gitgitgadget@gmail.com>
Date
Oct 1, 2019, 11:53 UTC
Message-ID
<pull.369.git.gitgitgadget@gmail.com>

I saw with sadness that pd/fetch-jobs went nowhere, and read in the most recent What's Cooking mail that it was even dropped.

This is my attempt to resurrect the idea (although without the overhead of trying to support a first-class UI to control submodule and multiple-remote fetches independently, of which I was a rather outspoken opponent).

To make things a bit safer, this patch uses the --end-of-options marker, and is therefore based on top of jk/eoo.

Johannes Schindelin (1):
  fetch: let --jobs=<n> parallelize --multiple, too
 Documentation/config/fetch.txt  |  10 +++
 Documentation/fetch-options.txt |  13 ++--
 builtin/fetch.c                 | 124 +++++++++++++++++++++++++++-----
 t/t5514-fetch-multiple.sh       |  11 +++
 4 files changed, 137 insertions(+), 21 deletions(-)
base-commit: 67feca3b1c45a51b204253039139b46cc07e145f
Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-369%2Fdscho%2Ffetch-jobs-v1
Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-369/dscho/fetch-jobs-v1
Pull-Request: https://github.com/gitgitgadget/git/pull/369
-- 
gitgitgadget
Next: Johannes Schindelin via GitGitGadget
Message 1 of 10 in “fetch --multiple: respect --jobs=”
  1. 0/1 fetch --multiple: respect --jobs=Johannes Schindelin via GitGitGadget, Oct 1, 2019
  2. 1/1 fetch: let --jobs=<n> parallelize --multiple, tooJohannes Schindelin via GitGitGadget, Oct 1, 2019
  3. Junio C HamanoOct 4, 2019
  4. Johannes SchindelinOct 4, 2019
  5. 0/1 fetch --multiple: respect --jobs=Johannes Schindelin via GitGitGadget, Oct 5, 2019
  6. 1/1 fetch: let --jobs=<n> parallelize --multiple, tooJohannes Schindelin via GitGitGadget, Oct 5, 2019
  7. Johannes SchindelinOct 6, 2019
  8. Junio C HamanoOct 7, 2019
  9. Johannes SchindelinOct 7, 2019
  10. Johannes SchindelinOct 7, 2019

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.