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

Re: multiple source file extensions

From
Junio C Hamano <gitster@pobox.com>
Date
May 3, 2015, 02:26 UTC
Message-ID
<xmqqfv7ewg53.fsf@gitster.dls.corp.google.com>
In-Reply-To
<CAPig+cT8kP0NrmXXn-chBU+zjM_28NT5CVivda2NDs_mxuepzQ@mail.gmail.com>
Eric Sunshine <sunshine@sunshineco.com> writes:
>> I agree we don't really need curly braces in pathspecs. :)
>
> However, neither POSIX shells nor the Windows command interpreter
> support curly-brace alternation.

Why "However"? Neither of them offer it because their users do not need it---why should we give it only when they are using Git and only for the in-repo contents (we obviously cannot help when their users want to refer to the working tree files)?

Previous: Eric SunshineNext: Jeff King
Message 8 of 13 in “multiple source file extensions”
  1. Thiago FarinaMay 2, 2015
  2. Josh HaginsMay 2, 2015
  3. Jeff KingMay 2, 2015
  4. Duy NguyenMay 2, 2015
  5. Duy NguyenMay 2, 2015
  6. Jeff KingMay 2, 2015
  7. Eric SunshineMay 2, 2015
  8. Junio C HamanoMay 3, 2015
  9. Jeff KingMay 2, 2015
  10. Thiago FarinaMay 4, 2015
  11. Jeff KingMay 5, 2015
  12. Mikael MagnussonMay 5, 2015
  13. Jeff KingMay 5, 2015

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.