Re: --jobs=0 no longer does any work
- From
Johannes Schindelin <johannes.schindelin@gmx.de>
- Date
- Mar 27, 2023, 09:19 UTC
- Message-ID
- <ed63b919-eb3a-1aae-0746-1ff582890a28@gmx.de>
- In-Reply-To
- <PSAP153MB03910458707331B64FA7460DCAA19@PSAP153MB0391.APCP153.PROD.OUTLOOK.COM>
Hi Drew,
On Fri, 17 Feb 2023, Drew Noakes wrote:
Show 16 quoted lines
> 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.
This should be fixed via https://github.com/git/git/commit/d180cc297922569e530da843bee4df3964167dea which made it into v2.40.0, unless I am mistaken. Could you verify?
Ciao, Johannes