Am 31.07.19 um 17:45 schrieb Alexandr Miloslavskiy: > Our suggestion is to change commands such as 'commit', 'add', etc to > also work with --stdin-paths. If a command already supports stdin for > any purpose, then trying to use both options will return an error.
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. René
