From: Stefan Beller <sbeller@google.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: What's cooking in git.git (Dec 2015, #05; Tue, 15)
Date: Tue, 15 Dec 2015 15:16:39 -0800 [thread overview]
Message-ID: <CAGZ79kaeixm3ACrUCuMD8eL_tuniKk5Y5Ote1n=75ExxhTL62g@mail.gmail.com> (raw)
In-Reply-To: <xmqq8u4ve3at.fsf@gitster.mtv.corp.google.com>
On Tue, Dec 15, 2015 at 2:48 PM, Junio C Hamano <gitster@pobox.com> wrote:
>
> * sb/submodule-parallel-fetch (2015-12-14) 8 commits
> - submodules: allow parallel fetching, add tests and documentation
> - fetch_populated_submodules: use new parallel job processing
> - run-command: add an asynchronous parallel child processor
> - sigchain: add command to pop all common signals
> - strbuf: add strbuf_read_once to read without blocking
> - xread_nonblock: add functionality to read from fds without blocking
> - xread: poll on non blocking fds
> - submodule.c: write "Fetching submodule <foo>" to stderr
> (this branch is used by sb/submodule-parallel-update.)
>
> Add a framework to spawn a group of processes in parallel, and use
> it to run "git fetch --recurse-submodules" in parallel.
>
> Rerolled and this seems to be a lot cleaner. The merge of the
> earlier one to 'next' has been reverted.
>
> Will merge to 'next' after a few days.
I plan on resending after the recent discussion, dropping xread_nonblock
and only have strbuf_read_once in there.
>
> * sb/submodule-parallel-update (2015-12-14) 8 commits
> - clone: allow an explicit argument for parallel submodule clones
> - submodule update: expose parallelism to the user
> - git submodule update: have a dedicated helper for cloning
> - fetching submodules: respect `submodule.fetchJobs` config option
> - submodule-config: introduce parse_generic_submodule_config
> - submodule-config: remove name_and_item_from_var
> - submodule-config: drop check against NULL
> - submodule-config: keep update strategy around
> (this branch uses sb/submodule-parallel-fetch.)
>
> Builds on top of the "fetch --recurse-submodules" work to introduce
> parallel downloading into multiple submodules for "submodule update".
>
> Needs review.
A while ago it had some review (specially bike shedding on the option name),
I did not change it substantially. I hope we don't get into bike
shedding the option
name again.
next prev parent reply other threads:[~2015-12-15 23:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-15 22:48 What's cooking in git.git (Dec 2015, #05; Tue, 15) Junio C Hamano
2015-12-15 23:16 ` Stefan Beller [this message]
2015-12-15 23:32 ` Jeff King
2015-12-15 23:34 ` Junio C Hamano
2015-12-15 23:36 ` Junio C Hamano
2015-12-15 23:44 ` Junio C Hamano
2015-12-16 0:50 ` Jeff King
2015-12-16 15:58 ` Johannes Schindelin
2015-12-16 6:58 ` Torsten Bögershausen
2015-12-16 18:04 ` Junio C Hamano
2015-12-21 15:31 ` Torsten Bögershausen
2015-12-18 13:23 ` SZEDER Gábor
2015-12-21 16:54 ` Junio C Hamano
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='CAGZ79kaeixm3ACrUCuMD8eL_tuniKk5Y5Ote1n=75ExxhTL62g@mail.gmail.com' \
--to=sbeller@google.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).