|
From: | Dmitry Gutov |
Subject: | bug#39452: [PATCH] vc-git-state fails for filenames with wildcards |
Date: | Fri, 14 Feb 2020 22:37:42 +0200 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0 |
On 14.02.2020 17:45, Eli Zaretskii wrote:
I won't argue. I just wanted to point out that using Git signatures internally might get in the way, whereas environment variables and command-line switches are free from that disadvantage.
Um, I think they're about the same in the level of convenience for us to be able to disable either: we can add a global var which would affect whether specs are interpreted literally.
If anything, approach #1 is slightly easier if we wanted to support opting out of literal-quoting the specs at the level of VC backend actions: certain action implementations can simply avoid calling the proposed functions (like vc-git--literal-pathspec). But then, I'm not sure that we want this capability at exactly that abstraction level.
[Prev in Thread] | Current Thread | [Next in Thread] |