From: Stefan Beller <sbeller@google.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>,
Jonathan Nieder <jrnieder@gmail.com>,
Jens Lehmann <Jens.Lehmann@web.de>
Subject: Re: [PATCHv7 0/8] Expose submodule parallelism to the user
Date: Wed, 13 Jan 2016 09:48:17 -0800 [thread overview]
Message-ID: <CAGZ79kaRyQXDiOQCdmBuEQdGevj7ebnmCtErVy4ymwPzLfrmtA@mail.gmail.com> (raw)
In-Reply-To: <xmqq37u1quyf.fsf@gitster.mtv.corp.google.com>
On Wed, Jan 13, 2016 at 8:56 AM, Junio C Hamano <gitster@pobox.com> wrote:
> Stefan Beller <sbeller@google.com> writes:
>
>> Additionally to that I needed to switch the order of arguments for the
>> parallel processing calls, too, to make it compile again.
>
> That sounds as if the previous one that was queued did not compile,
> but I didn't recall seeing such breakage. Also comparison between
> corresponding patches did not show such a change, either.
>
> But perhaps ...
>
>> I assume I just did that work twice as the previous version
>> ought to compile, too.
>
> ... means that you didn't need such a switch after all, and the
> re-sent series didn't have it.
My local state has had the switch, and I needed to make it before sending out
the latest version. I do not recall doing that to the previous version, but that
version is fine, too.
Which means I may have missed some review comment (if any) or
that I am forgetting things (I was on holidays for 3 weeks, barely touching
an electronic device).
>
> I am just making sure that I got the right version in my tree, so
> please don't behave as if I am accusing you that you advertised that
> you did more work than you actually did and go defensive ;-)
It should not sound as if I go defensive by being accused. I just want
to point out I may have missed a thing on my end, so double caution
for reviewers may be warranted. It was badly worded though.
> If the
> reason I didn't see one kind of change in the series I received is
> because it didn't have to be done and the description mistakenly
> said that such a change is included, that is perfectly fine.
>
> Thanks.
Thanks,
Stefan
next prev parent reply other threads:[~2016-01-13 17:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-11 19:41 [PATCHv7 0/8] Expose submodule parallelism to the user Stefan Beller
2016-01-11 19:41 ` [PATCHv7 1/8] submodule-config: keep update strategy around Stefan Beller
2016-01-11 19:41 ` [PATCHv7 2/8] submodule-config: drop check against NULL Stefan Beller
2016-01-11 19:41 ` [PATCHv7 3/8] submodule-config: remove name_and_item_from_var Stefan Beller
2016-01-11 19:41 ` [PATCHv7 4/8] submodule-config: introduce parse_generic_submodule_config Stefan Beller
2016-01-11 19:41 ` [PATCHv7 5/8] fetching submodules: respect `submodule.fetchJobs` config option Stefan Beller
2016-01-11 19:41 ` [PATCHv7 6/8] git submodule update: have a dedicated helper for cloning Stefan Beller
2016-01-11 19:42 ` [PATCHv7 7/8] submodule update: expose parallelism to the user Stefan Beller
2016-01-11 19:42 ` [PATCHv7 8/8] clone: allow an explicit argument for parallel submodule clones Stefan Beller
2016-01-12 23:50 ` [PATCHv7 0/8] Expose submodule parallelism to the user Junio C Hamano
2016-01-12 23:59 ` Stefan Beller
2016-01-13 16:56 ` Junio C Hamano
2016-01-13 17:48 ` Stefan Beller [this message]
2016-01-20 20:53 ` Junio C Hamano
-- strict thread matches above, loose matches on Subject: below --
2016-02-02 17:51 Stefan Beller
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=CAGZ79kaRyQXDiOQCdmBuEQdGevj7ebnmCtErVy4ymwPzLfrmtA@mail.gmail.com \
--to=sbeller@google.com \
--cc=Jens.Lehmann@web.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jrnieder@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.
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 NNTP newsgroup(s).