From: Alexandr Miloslavskiy <alexandr.miloslavskiy@syntevo.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Jeff King <peff@peff.net>, git@vger.kernel.org
Subject: Re: Support for --stdin-paths in commit, add, etc
Date: Fri, 2 Aug 2019 17:11:24 +0200 [thread overview]
Message-ID: <b736296c-c964-6096-bf36-99d31ccf8fee@syntevo.com> (raw)
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
next prev parent reply other threads:[~2019-08-02 15:11 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-31 15:45 Support for --stdin-paths in commit, add, etc Alexandr Miloslavskiy
2019-07-31 17:15 ` Junio C Hamano
2019-07-31 17:19 ` Jeff King
2019-07-31 21:21 ` Junio C Hamano
2019-08-01 13:25 ` Alexandr Miloslavskiy
2019-08-01 17:35 ` Phillip Wood
2019-08-01 20:26 ` Junio C Hamano
2019-08-01 20:40 ` Alexandr Miloslavskiy
2019-08-02 11:33 ` Johannes Schindelin
2019-08-02 11:45 ` Alexandr Miloslavskiy
2019-08-02 14:48 ` Johannes Schindelin
2019-08-02 14:52 ` Alexandr Miloslavskiy
2019-08-02 11:52 ` Alexandr Miloslavskiy
2019-08-02 14:47 ` Johannes Schindelin
2019-08-02 15:11 ` Alexandr Miloslavskiy [this message]
2019-08-01 14:26 ` René Scharfe
2019-08-01 14:33 ` Alexandr Miloslavskiy
2019-08-01 15:56 ` Junio C Hamano
2019-08-01 16:04 ` Alexandr Miloslavskiy
2019-08-01 20:45 ` Junio C Hamano
2019-08-01 20:51 ` Alexandr Miloslavskiy
2019-08-02 11:40 ` Johannes Schindelin
2019-08-02 11:44 ` Alexandr Miloslavskiy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b736296c-c964-6096-bf36-99d31ccf8fee@syntevo.com \
--to=alexandr.miloslavskiy@syntevo.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).