]> git.ipfire.org Git - thirdparty/git.git/commit - Documentation/fetch-options.txt
fetch: let --jobs=<n> parallelize --multiple, too
authorJohannes Schindelin <johannes.schindelin@gmx.de>
Sat, 5 Oct 2019 18:46:40 +0000 (11:46 -0700)
committerJunio C Hamano <gitster@pobox.com>
Sat, 5 Oct 2019 22:35:58 +0000 (07:35 +0900)
commitd54dea77dba081770fec7707110d8480ccaf9439
tree71d32c1695cf3ce28fd4090d19e24971db96e491
parent67feca3b1c45a51b204253039139b46cc07e145f
fetch: let --jobs=<n> parallelize --multiple, too

So far, `--jobs=<n>` only parallelizes submodule fetches/clones, not
`--multiple` fetches, which is unintuitive, given that the option's name
does not say anything about submodules in particular.

Let's change that. With this patch, also fetches from multiple remotes
are parallelized.

For backwards-compatibility (and to prepare for a use case where
submodule and multiple-remote fetches may need different parallelization
limits), the config setting `submodule.fetchJobs` still only controls
the submodule part of `git fetch`, while the newly-introduced setting
`fetch.parallel` controls both (but can be overridden for submodules
with `submodule.fetchJobs`).

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Documentation/config/fetch.txt
Documentation/fetch-options.txt
builtin/fetch.c
t/t5514-fetch-multiple.sh