From: Junio C Hamano <gitster@pobox.com>
To: "Daniel D. Beck via GitGitGadget" <gitgitgadget@gmail.com>
Cc: git@vger.kernel.org, "Jean-Noël Avila" <jn.avila@free.fr>,
"Daniel D. Beck" <daniel@ddbeck.com>
Subject: Re: [PATCH] doc: fetch: document `--jobs=0` behavior
Date: Thu, 19 Feb 2026 09:38:17 -0800 [thread overview]
Message-ID: <xmqq342w7hx2.fsf@gitster.g> (raw)
In-Reply-To: <pull.2047.git.1771443159369.gitgitgadget@gmail.com> (Daniel D. Beck via GitGitGadget's message of "Wed, 18 Feb 2026 19:32:39 +0000")
"Daniel D. Beck via GitGitGadget" <gitgitgadget@gmail.com> writes:
> From: "Daniel D. Beck" <daniel@ddbeck.com>
>
> 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 <daniel@ddbeck.com>
> ---
> 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=<n>`::
> Parallelize all forms of fetching up to _<n>_ 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
prev parent reply other threads:[~2026-02-19 17:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-18 19:32 [PATCH] doc: fetch: document `--jobs=0` behavior Daniel D. Beck via GitGitGadget
2026-02-19 11:39 ` Patrick Steinhardt
2026-02-19 18:59 ` Junio C Hamano
2026-02-20 8:51 ` Patrick Steinhardt
2026-02-24 9:47 ` Daniel Beck
2026-03-02 12:35 ` Johannes Schindelin
2026-03-02 19:33 ` Junio C Hamano
2026-02-19 17:38 ` Junio C Hamano [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqq342w7hx2.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=daniel@ddbeck.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=jn.avila@free.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox