Re: Support for --stdin-paths in commit, add, etc
- From
- Alexandr Miloslavskiy <alexandr.miloslavskiy@syntevo.com>
- Date
- Aug 2, 2019, 15:11 UTC
- Message-ID
- <b736296c-c964-6096-bf36-99d31ccf8fee@syntevo.com>
- In-Reply-To
- <nycvar.QRO.7.76.6.1908021641200.46@tvgsbejvaqbjf.bet>
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