submodule update: run at most one fetch job unless otherwise set
authorJunio C Hamano <redacted>
Thu, 13 Dec 2018 19:02:48 +0000 (11:02 -0800)
committerJunio C Hamano <redacted>
Fri, 14 Dec 2018 02:54:56 +0000 (11:54 +0900)
commite3a9d1aca92d90f2fdfbefd29827f7d7d210947e
tree288aef06d88da1f2555928bd97893fe0a29f87e0
parent5d826e972970a784bd7a7bdf587512510097b8c7
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 <redacted>
Signed-off-by: Junio C Hamano <redacted>
Signed-off-by: Stefan Beller <redacted>
Signed-off-by: Junio C Hamano <redacted>
builtin/submodule--helper.c
t/t5526-fetch-submodules.sh
git clone https://git.99rst.org/PROJECT