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 16:33:45 +0200
In-reply-to: <066cfd61-9700-e154-042f-fc9cffbd6346@web.de>
References: <a38bc928-7ccd-e2d9-b89b-23298e9fa95d@syntevo.com> <066cfd61-9700-e154-042f-fc9cffbd6346@web.de>
User-agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0

On 01.08.2019 16:26, René Scharfe wrote:

Would it make sense to have a --paths-file parameter instead


Both approaches (stdin or file) will work well for us. File sounds

easier from programming perspective. However, in previous discussion,there was some concern about possible security problems with this approach.

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

Prev by Date: Re: Support for --stdin-paths in commit, add, etc
Next by Date: RE: [PATCH] git-p4: close temporary file before removing
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