All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Stefan Beller <sbeller@google.com>
Cc: Jonathan Nieder <jrnieder@gmail.com>,
	"git\@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: What's cooking in git.git (Feb 2016, #08; Fri, 26)
Date: Sat, 27 Feb 2016 09:42:10 -0800	[thread overview]
Message-ID: <xmqqy4a6gidp.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <CAGZ79ka_3wr7uCLRjA6DqzSUOF8V+SVH_89WxPsx=jjucaWmMg@mail.gmail.com> (Stefan Beller's message of "Fri, 26 Feb 2016 15:57:15 -0800")

Stefan Beller <sbeller@google.com> writes:

> 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

      reply	other threads:[~2016-02-27 17:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-26 23:41 What's cooking in git.git (Feb 2016, #08; Fri, 26) Junio C Hamano
2016-02-26 23:57 ` Stefan Beller
2016-02-27 17:42   ` Junio C Hamano [this message]

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=xmqqy4a6gidp.fsf@gitster.mtv.corp.google.com \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=jrnieder@gmail.com \
    --cc=sbeller@google.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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.