From: Alexandr Miloslavskiy Date: Fri, 02 Aug 2019 15:11:24 GMT Subject: Re: Support for --stdin-paths in commit, add, etc Message-ID: In-Reply-To: On 02.08.2019 16:47, Johannes Schindelin wrote: > and definitely does *not* want to write a file. In this case it can use `--paths-file -`, which means stdin. > Zilch. So I find the advice you received, let's say, interesting. I understood that `--paths-file` is suggested to avoid possible stdin collisions in high-level commands. It seems that only plumbing commands accept --stdin for paths now. Both me and you are now trying to address high-level commands, which is new. This explains why grep doesn't currently find `--paths-file`. The approach sounds reasonable to me as a long-term strategy: 1) Won't require rework if someone wants file instead 2) stdin is still supported for those who want it 3) There's a way to avoid potential collisions in stdin