From: Drew Noakes <drnoakes@microsoft.com>
To: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: --jobs=0 no longer does any work
Date: Fri, 17 Feb 2023 01:54:49 +0000 [thread overview]
Message-ID: <PSAP153MB03910458707331B64FA7460DCAA19@PSAP153MB0391.APCP153.PROD.OUTLOOK.COM> (raw)
What did you do before the bug happened? (Steps to reproduce your issue)
- Enter a repo with multiple remotes
- Run: git fetch --all --prune --jobs=0
What did you expect to happen? (Expected behavior)
- Multiple remotes to be fetched in parallel
What happened instead? (Actual behavior)
- Nothing fetched and command exits quickly with no output
What's different between what you expected and what actually happened?
- That command used to work correctly. It now does nothing.
Anything else you want to add:
- The git-config documentation says of zero jobs in "fetch.parallel" that "A value of 0 will give some reasonable default. If unset, it defaults to 1.".
- This started happening after I updated my version of Git for Windows earlier today.
- Excluding the --jobs argument or passing a non-zero value works as expected.
Please review the rest of the bug report below.
You can delete any lines you don't wish to share.
[System Info]
git version:
git version 2.39.2.windows.1
cpu: x86_64
built from commit: a82fa99b36ddfd643e61ed45e52abe314687df67
sizeof-long: 4
sizeof-size_t: 8
shell-path: /bin/sh
feature: fsmonitor--daemon
uname: Windows 10.0 22621
compiler info: gnuc: 12.2
libc info: no libc information available
$SHELL (typically, interactive shell): C:\Program Files\Git\usr\bin\bash.exe
[Enabled Hooks]
next reply other threads:[~2023-02-17 1:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-17 1:54 Drew Noakes [this message]
2023-03-27 9:19 ` --jobs=0 no longer does any work Johannes Schindelin
2023-03-27 12:16 ` Drew Noakes
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=PSAP153MB03910458707331B64FA7460DCAA19@PSAP153MB0391.APCP153.PROD.OUTLOOK.COM \
--to=drnoakes@microsoft.com \
--cc=git@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).