From: Junio C Hamano <gitster@pobox.com>
To: Elia Pinto <gitter.spiros@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 000/144] Use the $( ... ) construct for command substitution instead of using the back-quotes
Date: Tue, 25 Mar 2014 09:20:58 -0700 [thread overview]
Message-ID: <xmqq61n2ntat.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: 1395680321-32427-1-git-send-email-gitter.spiros@gmail.com
Elia Pinto <gitter.spiros@gmail.com> writes:
> The patch is simple but involves a large number of files with different authors.
> Being simple I think it is wasteful to cc a large number of different people
> for doing a review.
We'd somehow need a way to parallelize the reviews, though. Being
simple is never an indication that the series is less likely to
contain bugs, and it often is an opposite. It is easier to slip
bugs in to a simple, repetitive and long patch.
next prev parent reply other threads:[~2014-03-25 16:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-24 16:56 [PATCH 000/144] Use the $( ... ) construct for command substitution instead of using the back-quotes Elia Pinto
2014-03-25 16:20 ` Junio C Hamano [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-03-25 8:24 Elia Pinto
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=xmqq61n2ntat.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=gitter.spiros@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).