From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Junio C Hamano <gitster@pobox.com>, Palmer Dabbelt <palmer@sifive.com>
Cc: git@vger.kernel.org
Subject: pd/fetch-jobs, was Re: What's cooking in git.git (Sep 2019, #01; Sat, 7)
Date: Wed, 11 Sep 2019 14:01:14 +0200 (CEST) [thread overview]
Message-ID: <nycvar.QRO.7.76.6.1909111359150.5377@tvgsbejvaqbjf.bet> (raw)
In-Reply-To: <xmqqd0gcm2zm.fsf@gitster-ct.c.googlers.com>
Hi Junio,
On Sat, 7 Sep 2019, Junio C Hamano wrote:
> * 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.
Ciao,
Dscho
next prev parent reply other threads:[~2019-09-11 12:01 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-07 17:26 What's cooking in git.git (Sep 2019, #01; Sat, 7) Junio C Hamano
2019-09-09 18:58 ` Denton Liu
2019-09-09 19:57 ` Junio C Hamano
2019-09-10 0:18 ` Denton Liu
2019-09-09 23:47 ` brian m. carlson
2019-09-10 0:19 ` Junio C Hamano
2019-09-28 23:31 ` Junio C Hamano
2019-09-28 23:35 ` brian m. carlson
2019-09-10 5:04 ` Martin Ågren
2019-09-10 18:23 ` Josh Steadmon
2019-09-11 1:03 ` Matheus Tavares Bernardino
2019-09-11 12:01 ` Johannes Schindelin [this message]
2019-09-12 18:02 ` pd/fetch-jobs, was " Junio C Hamano
2019-09-14 13:58 ` Palmer Dabbelt
2019-09-16 17:43 ` Junio C Hamano
2019-09-16 20:40 ` Palmer Dabbelt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=nycvar.QRO.7.76.6.1909111359150.5377@tvgsbejvaqbjf.bet \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=palmer@sifive.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).