From: Junio C Hamano <gitster@pobox•com>
To: Stefan Beller <sbeller@google•com>
Cc: git@vger•kernel.org, jrnieder@gmail•com, Jens.Lehmann@web•de,
peff@peff•net, sunshine@sunshineco•com
Subject: Re: [PATCHv14 0/7] Expose submodule parallelism to the user
Date: Fri, 19 Feb 2016 13:04:46 -0800 [thread overview]
Message-ID: <xmqqtwl4bedt.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <1455905833-7449-1-git-send-email-sbeller@google.com> (Stefan Beller's message of "Fri, 19 Feb 2016 10:17:06 -0800")
Looks good. I didn't notice these unnecessary blank lines while
reading the previous rounds, and it is good to see them go.
Let's wait for a few days and merge them to 'next'. David's ref
backend topic textually depends on this, and we'd better give it a
solid foundation to build on soon.
next prev parent reply other threads:[~2016-02-19 21:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-19 18:17 [PATCHv14 0/7] Expose submodule parallelism to the user Stefan Beller
2016-02-19 18:17 ` [PATCHv14 1/7] submodule-config: keep update strategy around Stefan Beller
2016-02-19 18:17 ` [PATCHv14 2/7] submodule-config: drop check against NULL Stefan Beller
2016-02-19 18:17 ` [PATCHv14 3/7] fetching submodules: respect `submodule.fetchJobs` config option Stefan Beller
2016-02-19 18:17 ` [PATCHv14 4/7] submodule update: direct error message to stderr Stefan Beller
2016-02-19 18:17 ` [PATCHv14 5/7] git submodule update: have a dedicated helper for cloning Stefan Beller
2016-02-19 23:07 ` Jonathan Nieder
2016-02-19 23:49 ` Stefan Beller
2016-02-20 0:32 ` Jonathan Nieder
2016-02-19 18:17 ` [PATCHv14 6/7] submodule update: expose parallelism to the user Stefan Beller
2016-02-19 18:17 ` [PATCHv14 7/7] clone: allow an explicit argument for parallel submodule clones Stefan Beller
2016-02-19 21:04 ` Junio C Hamano [this message]
2016-02-23 23:33 ` [PATCHv14 0/7] Expose submodule parallelism to the user Junio C Hamano
2016-02-23 23:42 ` Stefan Beller
2016-02-23 23:44 ` 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=xmqqtwl4bedt.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox$(echo .)com \
--cc=Jens.Lehmann@web$(echo .)de \
--cc=git@vger$(echo .)kernel.org \
--cc=jrnieder@gmail$(echo .)com \
--cc=peff@peff$(echo .)net \
--cc=sbeller@google$(echo .)com \
--cc=sunshine@sunshineco$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox