From: Junio C Hamano <gitster@pobox.com>
To: Stefan Beller <sbeller@google.com>
Cc: peff@peff.net, git@vger.kernel.org, jrnieder@gmail.com,
johannes.schindelin@gmail.com, Jens.Lehmann@web.de,
vlovich@gmail.com
Subject: Re: [PATCHv2] fetch submodules in parallel
Date: Mon, 14 Sep 2015 15:06:22 -0700 [thread overview]
Message-ID: <xmqqmvwoveox.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <1442267451-2527-1-git-send-email-sbeller@google.com> (Stefan Beller's message of "Mon, 14 Sep 2015 14:50:50 -0700")
Stefan Beller <sbeller@google.com> writes:
> This replaces the last patch of the "Parallel git submodule fetching"
> series. Changes:
>
> * have correct return code in submodule fetching when one submodule fails
> * use poll instead of select now
> * broke down into more smaller functions instead of one giant.
> (I think it is an improvement, but I wouldn't be surprised if someone objects)
> * closed memory leaks
> * document the need for stdout_to_stderr
>
> I don't deem it RFC-ish any more but good to go.
I didn't say this in the previous round because it smelled like an
RFC, but for a real submission, 2/2 may be doing too many things at
once. I suspect this is more or less "taste" thing, so I won't mind
too much as long as the reviewers are OK with it.
next prev parent reply other threads:[~2015-09-14 22:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-11 23:09 [RFC PATCHv1 0/2] Parallel git submodule fetching Stefan Beller
2015-09-11 23:09 ` [PATCH 1/2] Sending "Fetching submodule <foo>" output to stderr Stefan Beller
2015-09-11 23:09 ` [PATCH 2/2] fetch: fetch submodules in parallel Stefan Beller
2015-09-12 19:11 ` Junio C Hamano
2015-09-14 16:46 ` Stefan Beller
2015-09-14 17:17 ` Jeff King
2015-09-14 17:47 ` Stefan Beller
2015-09-14 17:55 ` Jonathan Nieder
2015-09-14 18:07 ` Jeff King
2015-09-14 21:50 ` [PATCHv2] " Stefan Beller
2015-09-14 21:50 ` [PATCHv2] fetch: " Stefan Beller
2015-09-14 22:06 ` Junio C Hamano [this message]
2015-09-14 17:56 ` [PATCH 2/2] " 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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqmvwoveox.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=Jens.Lehmann@web.de \
--cc=git@vger.kernel.org \
--cc=johannes.schindelin@gmail.com \
--cc=jrnieder@gmail.com \
--cc=peff@peff.net \
--cc=sbeller@google.com \
--cc=vlovich@gmail.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).