Alexandr Miloslavskiy writes:
> Johannes, thanks for working on this problem!
>
> In the previous discussion, there was a suggestion to change
> '--stdin' to '--paths-file', where '--paths-file -' would mean stdin:
> https://public-inbox.org/git/066cfd61-9700-e154-042f-fc9cffbd6...@web.de/
>
> I
Johannes, thanks for working on this problem!
In the previous discussion, there was a suggestion to change
'--stdin' to '--paths-file', where '--paths-file -' would mean stdin:
https://public-inbox.org/git/066cfd61-9700-e154-042f-fc9cffbd6...@web.de/
I believe that was a good suggestion for a fe
Eric Sunshine writes:
> On Wed, Sep 4, 2019 at 5:38 PM Johannes Schindelin via GitGitGadget
> wrote:
>> Just like with other Git commands, this option makes it read the paths
>> from the standard input. It comes in handy when resetting many, many
>> paths at once and wildcards are not an option
On Wed, Sep 4, 2019 at 5:38 PM Johannes Schindelin via GitGitGadget
wrote:
> Just like with other Git commands, this option makes it read the paths
> from the standard input. It comes in handy when resetting many, many
> paths at once and wildcards are not an option (e.g. when the paths are
> gene
4 matches
Mail list logo