All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Stefan Beller <sbeller@google.com>
Cc: Johannes Sixt <j6t@kdbg.org>,
	"git\@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: sb/submodule-parallel-fetch,
Date: Fri, 11 Dec 2015 15:07:22 -0800	[thread overview]
Message-ID: <xmqqvb84d1p1.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <CAGZ79kYOtoWHCzpeHGrCEjTUuKYB3rogfV2dxL_TL5Pcu59RSg@mail.gmail.com> (Stefan Beller's message of "Fri, 11 Dec 2015 14:52:53 -0800")

Stefan Beller <sbeller@google.com> writes:

> On Fri, Dec 11, 2015 at 1:37 PM, Johannes Sixt <j6t@kdbg.org> wrote:
>>
>> Generally, I'm already quite satisfied with the state of the
>> infrastructure at the tip of the branch.
>
> I was about the rework the patch series.

OK.

I think the very early part of the series, up to 8fc3f2ee (sigchain:
add command to pop all common signals, 2015-09-30), may be fine
as-is (i.e. just rebase on top of updated 'master').

The step after that, i.e. asynch processor, is the most interesting
and important one.  Since it was written, I think the improvements
that we want to be rolled into it from the beginning are:

 - do not rely on waitpid(-1);

 - no need for set_nonglocking(), squashing a4433fd4a and
   6f963a895a9 in;

 - correct the early-shutdown bug 79f38577 and again in 63ce47e1;

 - child_process_clear() in 1c53754a, which probably will become
   unnecessary if the series is rebuilt on top of updated 'master';

 - follow-up fixes and enhancements to the tests in c3a5d11 and
   74cc04d;

 - debugging support in 7eb93e91069 (from the other series that
   builds on top).

That would slim down not just the total number of patches, but also
the amount of the code that needs to be looked at (as we would not
add code only to later remove or fixup).

  reply	other threads:[~2015-12-11 23:07 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
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           ` Junio C Hamano [this message]
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=xmqqvb84d1p1.fsf@gitster.mtv.corp.google.com \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=j6t@kdbg.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.