From: Junio C Hamano <gitster@pobox.com>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>,
Elia Pinto <gitter.spiros@gmail.com>,
"git\@vger.kernel.org" <git@vger.kernel.org>,
Eric Sunshine <sunshine@sunshineco.com>
Subject: Re: Patch Series v3 for "use the $( ... ) construct for command substitution"
Date: Fri, 04 Apr 2014 12:27:48 -0700 [thread overview]
Message-ID: <xmqqa9c0q4i3.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <20140404181215.GJ6851@google.com> (Jonathan Nieder's message of "Fri, 4 Apr 2014 11:12:15 -0700")
Jonathan Nieder <jrnieder@gmail.com> writes:
> 140 patches worth of churn once every couple of years is not terrible,
> but I really don't want to see this becoming a pattern. :/
Likewise.
> And I don't see how the upside in this example warrants it.
Paraphrasing http://article.gmane.org/gmane.linux.kernel/943020
It'd be good if we don't _add_ such things to the tree.
But IMO it's such a minor thing that once it _is_ in the tree, it's
not really worth the patch noise to go and fix it up.
prev parent reply other threads:[~2014-04-04 19:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-04 16:52 Patch Series v3 for "use the $( ... ) construct for command substitution" Elia Pinto
2014-04-04 17:29 ` Jonathan Nieder
2014-04-04 17:40 ` Matthieu Moy
2014-04-04 18:12 ` Jonathan Nieder
2014-04-04 19:27 ` Junio C Hamano [this message]
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=xmqqa9c0q4i3.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--cc=Matthieu.Moy@grenoble-inp.fr \
--cc=git@vger.kernel.org \
--cc=gitter.spiros@gmail.com \
--cc=jrnieder@gmail.com \
--cc=sunshine@sunshineco.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.