Re: --jobs=0 no longer does any work

From: Drew Noakes <drnoakes@microsoft.com>
Date: Mar 27, 2023, 12:16 UTC
Message-ID: <PSAP153MB0391861D0B15BBA22D7D6E2CCA8B9@PSAP153MB0391.APCP153.PROD.OUTLOOK.COM>
In-Reply-To: <ed63b919-eb3a-1aae-0746-1ff582890a28@gmx.de>

Hi Johannes,

Fix verified in 2.40.0. Thank you for restoring this behaviour.

Best, Drew.

-----Original Message-----
From: Johannes Schindelin <Johannes.Schindelin@gmx.de> 
Sent: Monday, March 27, 2023 8:19 PM
To: Drew Noakes <drnoakes@microsoft.com>
Cc: git@vger.kernel.org
Subject: Re: --jobs=0 no longer does any work

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