{"thread":{"id":"59259","subject":"--jobs=0 no longer does any work","startedAt":"2023-02-17T01:55:05Z","lastAt":"2023-03-27T12:17:21Z","messageCount":3,"participants":["Drew Noakes","Johannes Schindelin"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"472244","messageId":"PSAP153MB03910458707331B64FA7460DCAA19@PSAP153MB0391.APCP153.PROD.OUTLOOK.COM","threadId":"59259","inReplyTo":null,"subject":"--jobs=0 no longer does any work","fromName":"Drew Noakes","fromEmail":"drnoakes@microsoft.com","sentAt":"2023-02-17T01:54:49Z","receivedAt":"2023-02-17T01:55:05Z","isPatch":false,"sender":{"key":"drnoakes@microsoft.com","avatar":null},"body":"What did you do before the bug happened? (Steps to reproduce your issue)\n\n- Enter a repo with multiple remotes\n- Run: git fetch --all --prune --jobs=0\n\nWhat did you expect to happen? (Expected behavior)\n\n- Multiple remotes to be fetched in parallel\n\nWhat happened instead? (Actual behavior)\n\n- Nothing fetched and command exits quickly with no output\n\nWhat's different between what you expected and what actually happened?\n\n- That command used to work correctly. It now does nothing.\n\nAnything else you want to add:\n\n- 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.\".\n- This started happening after I updated my version of Git for Windows earlier today.\n- Excluding the --jobs argument or passing a non-zero value works as expected.\n\nPlease review the rest of the bug report below.\nYou can delete any lines you don't wish to share.\n\n[System Info]\ngit version:\ngit version 2.39.2.windows.1\ncpu: x86_64\nbuilt from commit: a82fa99b36ddfd643e61ed45e52abe314687df67\nsizeof-long: 4\nsizeof-size_t: 8\nshell-path: /bin/sh\nfeature: fsmonitor--daemon\nuname: Windows 10.0 22621 \ncompiler info: gnuc: 12.2\nlibc info: no libc information available\n$SHELL (typically, interactive shell): C:\\Program Files\\Git\\usr\\bin\\bash.exe\n\n[Enabled Hooks]\n\n"},{"id":"474225","messageId":"ed63b919-eb3a-1aae-0746-1ff582890a28@gmx.de","threadId":"59259","inReplyTo":"PSAP153MB03910458707331B64FA7460DCAA19@PSAP153MB0391.APCP153.PROD.OUTLOOK.COM","subject":"Re: --jobs=0 no longer does any work","fromName":"Johannes Schindelin","fromEmail":"johannes.schindelin@gmx.de","sentAt":"2023-03-27T09:19:16Z","receivedAt":"2023-03-27T09:19:25Z","isPatch":false,"sender":{"key":"johannes.schindelin@gmx.de","avatar":"https://avatars.githubusercontent.com/u/127790?v=4"},"body":"Hi Drew,\n\nOn Fri, 17 Feb 2023, Drew Noakes wrote:\n\n> What did you do before the bug happened? (Steps to reproduce your issue)\n>\n> - Enter a repo with multiple remotes\n> - Run: git fetch --all --prune --jobs=0\n>\n> What did you expect to happen? (Expected behavior)\n>\n> - Multiple remotes to be fetched in parallel\n>\n> What happened instead? (Actual behavior)\n>\n> - Nothing fetched and command exits quickly with no output\n>\n> What's different between what you expected and what actually happened?\n>\n> - That command used to work correctly. It now does nothing.\n\nThis should be fixed via\nhttps://github.com/git/git/commit/d180cc297922569e530da843bee4df3964167dea\nwhich made it into v2.40.0, unless I am mistaken. Could you verify?\n\nCiao,\nJohannes\n"},{"id":"474233","messageId":"PSAP153MB0391861D0B15BBA22D7D6E2CCA8B9@PSAP153MB0391.APCP153.PROD.OUTLOOK.COM","threadId":"59259","inReplyTo":"ed63b919-eb3a-1aae-0746-1ff582890a28@gmx.de","subject":"Re: --jobs=0 no longer does any work","fromName":"Drew Noakes","fromEmail":"drnoakes@microsoft.com","sentAt":"2023-03-27T12:16:01Z","receivedAt":"2023-03-27T12:17:21Z","isPatch":false,"sender":{"key":"drnoakes@microsoft.com","avatar":null},"body":"Hi Johannes,\n\nFix verified in 2.40.0. Thank you for restoring this behaviour.\n\nBest,\nDrew.\n\n-----Original Message-----\nFrom: Johannes Schindelin <Johannes.Schindelin@gmx.de> \nSent: Monday, March 27, 2023 8:19 PM\nTo: Drew Noakes <drnoakes@microsoft.com>\nCc: git@vger.kernel.org\nSubject: Re: --jobs=0 no longer does any work\n\nHi Drew,\n\nOn Fri, 17 Feb 2023, Drew Noakes wrote:\n\n> What did you do before the bug happened? (Steps to reproduce your issue)\n>\n> - Enter a repo with multiple remotes\n> - Run: git fetch --all --prune --jobs=0\n>\n> What did you expect to happen? (Expected behavior)\n>\n> - Multiple remotes to be fetched in parallel\n>\n> What happened instead? (Actual behavior)\n>\n> - Nothing fetched and command exits quickly with no output\n>\n> What's different between what you expected and what actually happened?\n>\n> - That command used to work correctly. It now does nothing.\n\nThis should be fixed via\nhttps://github.com/git/git/commit/d180cc297922569e530da843bee4df3964167dea\nwhich made it into v2.40.0, unless I am mistaken. Could you verify?\n\nCiao,\nJohannes\n"}]}