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

Re: [PATCHv7 0/8] Expose submodule parallelism to the user

From
Stefan Beller <sbeller@google.com>
Date
Jan 13, 2016, 17:48 UTC
Message-ID
<CAGZ79kaRyQXDiOQCdmBuEQdGevj7ebnmCtErVy4ymwPzLfrmtA@mail.gmail.com>
In-Reply-To
<xmqq37u1quyf.fsf@gitster.mtv.corp.google.com>
On Wed, Jan 13, 2016 at 8:56 AM, Junio C Hamano <gitster@pobox.com> wrote:
Show 16 quoted lines
> Stefan Beller <sbeller@google.com> writes:
>
>> Additionally to that I needed to switch the order of arguments for the
>> parallel processing calls, too, to make it compile again.
>
> That sounds as if the previous one that was queued did not compile,
> but I didn't recall seeing such breakage.  Also comparison between
> corresponding patches did not show such a change, either.
>
> But perhaps ...
>
>> I assume I just did that work twice as the previous version
>> ought to compile, too.
>
> ... means that you didn't need such a switch after all, and the
> re-sent series didn't have it.

My local state has had the switch, and I needed to make it before sending out the latest version. I do not recall doing that to the previous version, but that version is fine, too.

Which means I may have missed some review comment (if any) or that I am forgetting things (I was on holidays for 3 weeks, barely touching an electronic device).

>
> I am just making sure that I got the right version in my tree, so
> please don't behave as if I am accusing you that you advertised that
> you did more work than you actually did and go defensive ;-)

It should not sound as if I go defensive by being accused. I just want to point out I may have missed a thing on my end, so double caution for reviewers may be warranted. It was badly worded though.

Show 6 quoted lines
>  If the
> reason I didn't see one kind of change in the series I received is
> because it didn't have to be done and the description mistakenly
> said that such a change is included, that is perfectly fine.
>
> Thanks.

Thanks, Stefan

Previous: Junio C HamanoNext: Junio C Hamano
Message 13 of 14 in “[PATCHv7 0/8] Expose submodule parallelism to the user”
  1. Stefan BellerJan 11, 2016
  2. 1/8 submodule-config: keep update strategy aroundStefan Beller, Jan 11, 2016
  3. 2/8 submodule-config: drop check against NULLStefan Beller, Jan 11, 2016
  4. 3/8 submodule-config: remove name_and_item_from_varStefan Beller, Jan 11, 2016
  5. 4/8 submodule-config: introduce parse_generic_submodule_configStefan Beller, Jan 11, 2016
  6. 5/8 fetching submodules: respect `submodule.fetchJobs` config optionStefan Beller, Jan 11, 2016
  7. 6/8 git submodule update: have a dedicated helper for cloningStefan Beller, Jan 11, 2016
  8. 7/8 submodule update: expose parallelism to the userStefan Beller, Jan 11, 2016
  9. 8/8 clone: allow an explicit argument for parallel submodule clonesStefan Beller, Jan 11, 2016
  10. Junio C HamanoJan 12, 2016
  11. Stefan BellerJan 12, 2016
  12. Junio C HamanoJan 13, 2016
  13. Stefan BellerJan 13, 2016
  14. Junio C HamanoJan 20, 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.