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

Re: pd/fetch-jobs, was Re: What's cooking in git.git (Sep 2019, #01; Sat, 7)

From
Palmer Dabbelt <palmer@sifive.com>
Date
Sep 14, 2019, 13:58 UTC
Message-ID
<mhng-2c9b8fd0-22e7-4679-9d9b-f8128881fada@palmer-si-x1e>
In-Reply-To
<xmqq8sqtgzp9.fsf@gitster-ct.c.googlers.com>
On Thu, 12 Sep 2019 11:02:42 PDT (-0700), gitster@pobox.com wrote:
Show 26 quoted lines
> Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
>
>>> * pd/fetch-jobs (2019-08-13) 5 commits
>>>  . fetch: make --jobs control submodules and remotes
>>>  . fetch: add the --submodule-fetch-jobs option
>>>  . fetch: add the fetch.jobs config key
>>>  . fetch: add the "--fetch-jobs" option
>>>  . fetch: rename max_children to max_children_for_submodules
>>>
>>>  "git fetch --jobs" is getting taught to also run fetch jobs in
>>>  parallel when fetching from multiple remote repositories.
>>>
>>>  Comments?
>>
>> I still stand by my suggestion that it is undesirable (and makes the
>> code much more complicated than necessary) to end up with three options.
>> Having only `--jobs=<n>` would be the ideal solution.
>
> I think exposing "--jobs" as the primary UI element is a good longer
> term goal; the approach taken in the intermediate step would be a
> necessary one for backward compatibility.
>
> I stopped carrying it in 'pu' some weeks ago (I suspect it had some
> interactions with other topics in flight, by causing either test
> failures or textual conflicts).  Perhaps somebody interested enough
> in the topic can resurrect it.

Sorry, I'm somewhat new to the git development process. I'm happy to re-spin the patch set, I'm just not sure what do to here. It looks like there are some test failures when I rebase to the latest master, which I'm happy to fix. Just let me know if I should:

* Send all 5 patches, under the assumption that the last one will not get 
  merged until some time later.
* Send just the first 4 patches, holding onto the last one for later.
* Send just a single patch, which wouldn't add the --fetch-jobs and 
  --submodule-fetch-jobs arguments.
Previous: Junio C HamanoNext: Junio C Hamano
Message 14 of 16 in “What's cooking in git.git (Sep 2019, #01; Sat, 7)”
  1. Junio C HamanoSep 7, 2019
  2. Denton LiuSep 9, 2019
  3. Junio C HamanoSep 9, 2019
  4. Denton LiuSep 10, 2019
  5. brian m. carlsonSep 9, 2019
  6. Junio C HamanoSep 10, 2019
  7. Junio C HamanoSep 28, 2019
  8. brian m. carlsonSep 28, 2019
  9. Martin ÅgrenSep 10, 2019
  10. Josh SteadmonSep 10, 2019
  11. Matheus Tavares BernardinoSep 11, 2019
  12. pd/fetch-jobs, was Re: What's cooking in git.git (Sep 2019, #01; Sat, 7)Johannes Schindelin, Sep 11, 2019
  13. Junio C HamanoSep 12, 2019
  14. Palmer DabbeltSep 14, 2019
  15. Junio C HamanoSep 16, 2019
  16. Palmer DabbeltSep 16, 2019

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.