git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCHv20 00/12] Expose submodule parallelism to the user

From
Junio C Hamano <gitster@pobox.com>
Date
Feb 29, 2016, 20:50 UTC
Message-ID
<xmqq60x79r7k.fsf@gitster.mtv.corp.google.com>
In-Reply-To
<20160229193222.GX28749@google.com>
Jonathan Nieder <jrnieder@gmail.com> writes:
Show 6 quoted lines
> Stefan Beller wrote:
>
>> I added your suggestions as amending and as a new patch.
>
> I think we're at the point where patches on top would work better.  I
> admit I was a little scared to see another reroll.

Yup, let's stop rerolling this during pre-release period, and instead concentrate on fixing what's already in 'master' ;-)

Previous: Stefan Beller
Message 16 of 16 in “[PATCHv20 00/12] Expose submodule parallelism to the user”
  1. Stefan BellerFeb 29, 2016
  2. 01/12 submodule-config: keep update strategy aroundStefan Beller, Feb 29, 2016
  3. 02/12 submodule-config: drop check against NULLStefan Beller, Feb 29, 2016
  4. 03/12 fetching submodules: respect `submodule.fetchJobs` config optionStefan Beller, Feb 29, 2016
  5. 04/12 submodule update: direct error message to stderrStefan Beller, Feb 29, 2016
  6. 05/12 run_processes_parallel: treat output of children as byte arrayStefan Beller, Feb 29, 2016
  7. 06/12 run-command: expose default_{start_failure, task_finished}Stefan Beller, Feb 29, 2016
  8. 07/12 run_processes_parallel: rename parameters for the callbacksStefan Beller, Feb 29, 2016
  9. 08/12 run_processes_parallel: correctly terminate callbacks with an LFStefan Beller, Feb 29, 2016
  10. 09/12 git submodule update: have a dedicated helper for cloningStefan Beller, Feb 29, 2016
  11. 10/12 submodule helper: remove double 'fatal: ' prefixStefan Beller, Feb 29, 2016
  12. 11/12 submodule update: expose parallelism to the userStefan Beller, Feb 29, 2016
  13. 12/12 clone: allow an explicit argument for parallel submodule clonesStefan Beller, Feb 29, 2016
  14. Jonathan NiederFeb 29, 2016
  15. Stefan BellerFeb 29, 2016
  16. Junio C HamanoFeb 29, 2016

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.