git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Patch Series v3 for "use the $( ... ) construct for command substitution"

From
Junio C Hamano <gitster@pobox.com>
Date
Apr 4, 2014, 19:27 UTC
Message-ID
<xmqqa9c0q4i3.fsf@gitster.dls.corp.google.com>
In-Reply-To
<20140404181215.GJ6851@google.com>
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.

Previous: Jonathan Nieder
Message 5 of 5 in “Patch Series v3 for "use the $( ... ) construct for command substitution"”
  1. Elia PintoApr 4, 2014
  2. Jonathan NiederApr 4, 2014
  3. Matthieu MoyApr 4, 2014
  4. Jonathan NiederApr 4, 2014
  5. Junio C HamanoApr 4, 2014

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.