Re: Support for --stdin-paths in commit, add, etc

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: Re: Support for --stdin-paths in commit, add, etc
From: Alexandr Miloslavskiy <alexandr.miloslavskiy@xxxxxxxxxxx>
Date: Thu, 1 Aug 2019 18:04:17 +0200
Cc: git@xxxxxxxxxxxxxxx
In-reply-to: <xmqqef24op5q.fsf@gitster-ct.c.googlers.com>
References: <a38bc928-7ccd-e2d9-b89b-23298e9fa95d@syntevo.com> <066cfd61-9700-e154-042f-fc9cffbd6346@web.de> <xmqqef24op5q.fsf@gitster-ct.c.googlers.com>
User-agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0

On 01.08.2019 17:56, Junio C Hamano wrote:

So, reading paths from a file (which could be "-" as you suggest)
would be a good solution for that.


To summarize:
1) Implement --paths-file for high-level commands.
2) '--paths-file -' would mean reading from stdin.

Is that something you're ready to accept patches for?

Follow-Ups:
- Re: Support for --stdin-paths in commit, add, etc
  - From: Junio C Hamano

References:
- Support for --stdin-paths in commit, add, etc
  - From: Alexandr Miloslavskiy
- Re: Support for --stdin-paths in commit, add, etc
  - From: René Scharfe
- Re: Support for --stdin-paths in commit, add, etc
  - From: Junio C Hamano

Prev by Date: Re: [PATCH] RelNotes/2.23.0: fix a few typos and other minor issues
Next by Date: [PATCH v2] checkout.c: unstage empty deleted ita files
Previous by thread: Re: Support for --stdin-paths in commit, add, etc
Next by thread: Re: Support for --stdin-paths in commit, add, etc
Index(es):
- Date
- Thread

[Index of Archives] [Linux Kernel Development] [Gcc Help] [IETF Annouce] [DCCP] [Netdev] [Networking] [Security] [V4L] [Bugtraq] [Yosemite] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Linux SCSI] [Fedora Users]

Powered by Linux