On Thu, Aug 16, 2018 at 12:41 AM Martin Ågren <martin.agren@xxxxxxxxx> wrote: > On Wed, 15 Aug 2018 at 22:56, Elia Pinto <gitter.spiros@xxxxxxxxx> wrote: > The word "currently" means I can't shake the feeling that Eric has a > very good point in [1]: > > It might make sense to say instead that this is adding a --quiet > option _in general_, rather than doing so specifically for 'add'. > > As an example, if `git worktree move` ever learns to produce some sort > of output, then Eric's approach would mean that such a hypothetical > `move` is buggy until it learns to respect `--quiet`. With your > approach, it would mean that we would get feature requests that `move` > should also respect `--quiet` [...] > > Doing such a patch instead would mean tweaking the commit message > slightly... > > Add the '--quiet' option to git worktree, as for the other git > commands. Currently, 'add' is the only command affected by it since > all other commands, except 'list' obviously, are already silent by > default. > > ... and the documentation slightly ... > > Suppress feedback messages. This is a sensible suggestion for the documentation rather than having it call out "add" as special (unlike the commit message in which case it makes sense to mention that only the behavior of "add" is affected). > It might make sense adding a comment to the documentation about how this > currently only affects `add`, but such comments do risk going stale. Let's not mention "add" or any other command specially since the option is meant to be general. > I am on the fence about whether the documentation needs to say something > about `list` -- who in their right mind would expect `list --quiet` to > actually suppress the list? (/me nudges Martin off the fence onto the side of not bothering to mention the obvious) > Others might disagree violently with this, but I wonder whether it makes > sense to add a test to verify that, e.g., `git worktree move --quiet` is > quiet. Such a test would demonstrate that this is your intention, i.e., > anyone digging into a report on "why does git worktree foo not respect > --quiet?" would be 100% convinced that your intention back in 2018 really > was to respect it everywhere. It seems wasteful to add such a test for > all other modes, but maybe you can identify one which you think has a > higher risk of learning to output some feedback in the future. My knee-jerk reaction was that such tests seem unnecessary, but I think you convinced me that they would make sense to avoid future headaches since --quiet should indeed mean "quiet" generally. (Newly added worktree commands would not be protected by such tests added today, so it's not foolproof, but still better than nothing.) Having said that, though, lack of such tests shouldn't block this patch from being accepted. They can always be added later if someone wants to do it.
