Re: What's cooking in git.git (Feb 2016, #08; Fri, 26)
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Feb 27, 2016, 17:42 UTC
- Message-ID
- <xmqqy4a6gidp.fsf@gitster.mtv.corp.google.com>
- In-Reply-To
- <CAGZ79ka_3wr7uCLRjA6DqzSUOF8V+SVH_89WxPsx=jjucaWmMg@mail.gmail.com>
Stefan Beller <sbeller@google.com> writes:
Show 23 quoted lines
> On Fri, Feb 26, 2016 at 3:41 PM, Junio C Hamano <gitster@pobox.com> wrote:
>
>> * sb/submodule-parallel-update (2016-02-25) 11 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
>> - run_processes_parallel: correctly terminate callbacks with an LF
>> - run_processes_parallel: rename parameters for the callbacks
>> - run-command: expose default_{start_failure, task_finished}
>> - run_processes_parallel: treat output of children as byte array
>> - submodule update: direct error message to stderr
>> - fetching submodules: respect `submodule.fetchJobs` config option
>> - submodule-config: drop check against NULL
>> - submodule-config: keep update strategy around
>> (this branch is used by dt/refs-backend-lmdb and sb/submodule-init.)
>>
>> A major part of "git submodule update" has been ported to C to take
>> advantage of the recently added framework to run download tasks in
>> parallel.
>>
>> Seems to break tests when merged to the tip of 'pu'.
>
> There was a version (v17[1]) which broke tests,I think the series was updated and this comment was left stale. Will be fixed in the next issue.
Thanks