From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: AS31976 209.132.180.0/23 X-Spam-Status: No, score=-4.0 required=3.0 tests=AWL,BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,RCVD_IN_DNSWL_HI, SPF_HELO_NONE,SPF_NONE shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by dcvr.yhbt.net (Postfix) with ESMTP id 753A81F731 for ; Fri, 2 Aug 2019 15:11:27 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729319AbfHBPL0 (ORCPT ); Fri, 2 Aug 2019 11:11:26 -0400 Received: from smtprelay04.ispgateway.de ([80.67.31.38]:11435 "EHLO smtprelay04.ispgateway.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726044AbfHBPL0 (ORCPT ); Fri, 2 Aug 2019 11:11:26 -0400 Received: from [87.165.18.83] (helo=[192.168.2.6]) by smtprelay04.ispgateway.de with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.92) (envelope-from ) id 1htZDH-0002IL-EB; Fri, 02 Aug 2019 17:11:23 +0200 Subject: Re: Support for --stdin-paths in commit, add, etc To: Johannes Schindelin Cc: Jeff King , git@vger.kernel.org References: <20190731171956.GA26746@sigill.intra.peff.net> From: Alexandr Miloslavskiy Message-ID: Date: Fri, 2 Aug 2019 17:11:24 +0200 User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-GB Content-Transfer-Encoding: 7bit X-Df-Sender: YWxleGFuZHIubWlsb3NsYXZza2l5QHN5bnRldm8uY29t Sender: git-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org 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