On Tue, Dec 15, 2015 at 2:48 PM, Junio C Hamano <gitster@xxxxxxxxx> 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. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html