| commit | e3a9d1aca92d90f2fdfbefd29827f7d7d210947e | |
| author | Junio C Hamano <gitster@pobox.com> | |
| Thu, 13 Dec 2018 19:02:48 +0000 (13 11:02 -0800) | ||
| committer | Junio C Hamano <gitster@pobox.com> | |
| Fri, 14 Dec 2018 02:54:56 +0000 (14 11:54 +0900) | ||
| tree | 288aef06d88da1f2555928bd97893fe0a29f87e0 | treesnapshot (tar.gz zip) |
| parent | 5d826e972970a784bd7a7bdf587512510097b8c7 | commitdiff |
submodule update: run at most one fetch job unless otherwise set
In a028a1930c (fetching submodules: respect `submodule.fetchJobs`
config option, 2016-02-29), we made sure to keep the default
behavior of fetching at most one submodule at once when not setting
the newly introduced `submodule.fetchJobs` config.
This regressed in 90efe595c5 (builtin/submodule--helper: factor
out submodule updating, 2018-08-03). Fix it.
Reported-by: Sjon Hortensius <sjon@parse.nl>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Signed-off-by: Stefan Beller <sbeller@google.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
In a028a1930c (fetching submodules: respect `submodule.fetchJobs`
config option, 2016-02-29), we made sure to keep the default
behavior of fetching at most one submodule at once when not setting
the newly introduced `submodule.fetchJobs` config.
This regressed in 90efe595c5 (builtin/submodule--helper: factor
out submodule updating, 2018-08-03). Fix it.
Reported-by: Sjon Hortensius <sjon@parse.nl>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Signed-off-by: Stefan Beller <sbeller@google.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
| builtin/submodule--helper.c | diffblobblamehistory | |
| t/t5526-fetch-submodules.sh | diffblobblamehistory |