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

Re: Support for --stdin-paths in commit, add, etc

From
Junio C Hamano <gitster@pobox.com>
Date
Aug 1, 2019, 15:56 UTC
Message-ID
<xmqqef24op5q.fsf@gitster-ct.c.googlers.com>
In-Reply-To
<066cfd61-9700-e154-042f-fc9cffbd6346@web.de>
René Scharfe <l.s.r@web.de> writes:
Show 5 quoted lines
> Would it make sense to have a --paths-file parameter instead that allows
> reading paths from a given file and honors the convention of reading
> from stdin with the special argument "-"?  Reading from stdin would
> still only work for one parameter at a time, but paths could also be
> passed via a regular file or named pipe, allowing for more flexibility.

The command's primary function itself may want to use the standard input stream to read things other than the list of paths; if we are not limiting ourselves to plumbing (i.e. doing one thing well), the "--stdin-paths" may not be a general solution that is good enough.

So, reading paths from a file (which could be "-" as you suggest) would be a good solution for that.

Previous: Alexandr MiloslavskiyNext: Alexandr Miloslavskiy
Message 18 of 23 in “Support for --stdin-paths in commit, add, etc”
  1. Alexandr MiloslavskiyJul 31, 2019
  2. Junio C HamanoJul 31, 2019
  3. Jeff KingJul 31, 2019
  4. Junio C HamanoJul 31, 2019
  5. Alexandr MiloslavskiyAug 1, 2019
  6. Phillip WoodAug 1, 2019
  7. Junio C HamanoAug 1, 2019
  8. Alexandr MiloslavskiyAug 1, 2019
  9. Johannes SchindelinAug 2, 2019
  10. Alexandr MiloslavskiyAug 2, 2019
  11. Johannes SchindelinAug 2, 2019
  12. Alexandr MiloslavskiyAug 2, 2019
  13. Alexandr MiloslavskiyAug 2, 2019
  14. Johannes SchindelinAug 2, 2019
  15. Alexandr MiloslavskiyAug 2, 2019
  16. René ScharfeAug 1, 2019
  17. Alexandr MiloslavskiyAug 1, 2019
  18. Junio C HamanoAug 1, 2019
  19. Alexandr MiloslavskiyAug 1, 2019
  20. Junio C HamanoAug 1, 2019
  21. Alexandr MiloslavskiyAug 1, 2019
  22. Johannes SchindelinAug 2, 2019
  23. Alexandr MiloslavskiyAug 2, 2019

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.