Junio C Hamano <gits...@pobox.com> writes:
> Matthieu Moy <matthieu....@imag.fr> writes:
>> Most git commands that can be used with our without a filepattern are
>> tree-wide by default, the filepattern being used to restrict their scope.
>> A few exceptions are: 'git grep', 'git clean', 'git add -u' and 'git add -A'.
>> The inconsistancy of 'git add -u' and 'git add -A' are particularly
Thanks, will fix.
> I wonder if we want to say in the message
> The behaviour of 'git add --all (or -A)'...
> otherwise people who typed "git add -A" and got this message with
> just "--all" may go "Huh?" for a brief moment. I however do not
> think replacing these strings to
> option_with_implicit_dot = "--all (-A)";
> is a solution, given they are goven to _("l10n template %s").
Plus, option_with_implicit_dot is used in cut-and-paste ready commands
below. I can easily add another variable short_option or so to display
both. Ideally, we should use whatever the user had typed, but that does
not seem easy to do with parse-option so I'd say it's overkill.
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html