All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Stefan Beller <sbeller@google.com>
Cc: "git\@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: What's cooking in git.git (Dec 2015, #03; Thu, 10)
Date: Thu, 10 Dec 2015 15:51:54 -0800	[thread overview]
Message-ID: <xmqqvb85g8v9.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <CAGZ79kaA6Lo1W-SudX6v5styyGrX-igGC7i=u5AYOvFYK0DOGA@mail.gmail.com> (Stefan Beller's message of "Thu, 10 Dec 2015 15:25:46 -0800")

Stefan Beller <sbeller@google.com> writes:

>> * sb/submodule-parallel-fetch (2015-11-24) 17 commits
>> ...
>
> I assume you plan on merging this after 2.7 settled and then we can
> also get the above sb/submodule-parallel-update going again.

Yeah, thanks for reminding me.  I think that would be a good plan
that gives us an opportunity to clean up this topic, some parts of
which are have "an early patch that was too hastily merged to 'next'
had to be tweaked by an 'oops' follow-up patch in the topic"
pattern, e.g. "make waitpid the secondary and closed pipe the
primary way to monitor children".

Thanks.

  parent reply	other threads:[~2015-12-10 23:52 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-10 22:46 What's cooking in git.git (Dec 2015, #03; Thu, 10) Junio C Hamano
2015-12-10 23:25 ` Stefan Beller
2015-12-10 23:33   ` Junio C Hamano
2015-12-10 23:51   ` Junio C Hamano [this message]
2015-12-10 23:55     ` Stefan Beller
2015-12-11 17:39       ` Junio C Hamano
2015-12-11 21:37       ` sb/submodule-parallel-fetch, was: " Johannes Sixt
2015-12-11 22:52         ` Stefan Beller
2015-12-11 23:07           ` sb/submodule-parallel-fetch, Junio C Hamano
2015-12-14 19:37             ` sb/submodule-parallel-fetch, Stefan Beller
2015-12-11 23:39           ` sb/submodule-parallel-fetch, was: Re: What's cooking in git.git (Dec 2015, #03; Thu, 10) Johannes Sixt
2015-12-11  0:18 ` John Keeping
2015-12-11 17:43   ` 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

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

  git send-email \
    --in-reply-to=xmqqvb85g8v9.fsf@gitster.mtv.corp.google.com \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --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.