From: Junio C Hamano Date: Thu, 19 Feb 2026 17:38:17 GMT Subject: Re: [PATCH] doc: fetch: document `--jobs=0` behavior Message-ID: In-Reply-To: "Daniel D. Beck via GitGitGadget" writes: > From: "Daniel D. Beck" > > In c39952b92 (fetch: choose a sensible default with --jobs=0 again, > 2023-02-20), the `--jobs=0` behavior was (re)introduced, but it went > undocumented. Since this is the same behavior as `git -c fetch.parallel=0 > fetch`, which is documented, this change creates symmetry between the two > documentation sections. Makes sense. In hindsight, we might have been better off if we also called this "--jobs=auto", but documenting the behaviour is a good first step. Will queue. Thanks. > > Signed-off-by: Daniel D. Beck > --- > doc: fetch: document --jobs=0 behavior > > Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-2047%2Fddbeck%2Fdoc-git-fetch-jobs-0-v1 > Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-2047/ddbeck/doc-git-fetch-jobs-0-v1 > Pull-Request: https://github.com/gitgitgadget/git/pull/2047 > > Documentation/fetch-options.adoc | 2 ++ > 1 file changed, 2 insertions(+) > > diff --git a/Documentation/fetch-options.adoc b/Documentation/fetch-options.adoc > index fcba46ee9e..e15cbc51f2 100644 > --- a/Documentation/fetch-options.adoc > +++ b/Documentation/fetch-options.adoc > @@ -234,6 +234,8 @@ endif::git-pull[] > `--jobs=`:: > Parallelize all forms of fetching up to __ jobs at a time. > + > +A value of 0 will use some reasonable default. > ++ > If the `--multiple` option was specified, the different remotes will be fetched > in parallel. If multiple submodules are fetched, they will be fetched in > parallel. To control them independently, use the config settings > > base-commit: 852829b3dd2fe4e7c7fc4d8badde644cf1b66c74