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

Re: [PATCHv14 0/7] Expose submodule parallelism to the user

From
Junio C Hamano <gitster@pobox.com>
Date
Feb 23, 2016, 23:33 UTC
Message-ID
<xmqq8u2bngsi.fsf@gitster.mtv.corp.google.com>
In-Reply-To
<xmqqtwl4bedt.fsf@gitster.mtv.corp.google.com>
Junio C Hamano <gitster@pobox.com> writes:
Show 6 quoted lines
> Looks good.  I didn't notice these unnecessary blank lines while
> reading the previous rounds, and it is good to see them go.
>
> Let's wait for a few days and merge them to 'next'.  David's ref
> backend topic textually depends on this, and we'd better give it a
> solid foundation to build on soon.

So... it seems that you and Jonathan had a few rounds of back and forth on 5/7 that didn't sound like it saw a satisfactory end. Will we see a reroll to address the issues raised?

Thanks.
Previous: Junio C HamanoNext: Stefan Beller
Message 13 of 15 in “[PATCHv14 0/7] Expose submodule parallelism to the user”
  1. Stefan BellerFeb 19, 2016
  2. 1/7 submodule-config: keep update strategy aroundStefan Beller, Feb 19, 2016
  3. 2/7 submodule-config: drop check against NULLStefan Beller, Feb 19, 2016
  4. 3/7 fetching submodules: respect `submodule.fetchJobs` config optionStefan Beller, Feb 19, 2016
  5. 4/7 submodule update: direct error message to stderrStefan Beller, Feb 19, 2016
  6. 5/7 git submodule update: have a dedicated helper for cloningStefan Beller, Feb 19, 2016
  7. Jonathan NiederFeb 19, 2016
  8. Stefan BellerFeb 19, 2016
  9. Jonathan NiederFeb 20, 2016
  10. 6/7 submodule update: expose parallelism to the userStefan Beller, Feb 19, 2016
  11. 7/7 clone: allow an explicit argument for parallel submodule clonesStefan Beller, Feb 19, 2016
  12. Junio C HamanoFeb 19, 2016
  13. Junio C HamanoFeb 23, 2016
  14. Stefan BellerFeb 23, 2016
  15. Junio C HamanoFeb 23, 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.