Hello Junio,
On 2024-02-20 01:52, Junio C Hamano wrote:
Dragan Simic <dsimic@xxxxxxxxxxx> writes:
There's only one "Fixes" tag, while there should actually be a whole
bunch
of them to cover all the patches that introduced the configuration
parameter
names fixed by this patch. I think we're fine with just one.
I suspect that we are even better off without any. The only reason
to have them is if we plan to cherry-pick this patch down to a
separate maintenance track that the "culprit" was cherry-picked or
merged to, but we typically do not do so, and if we want to do so,
we'd need a much better coverage.
Agreed, will drop the single "Fixes" tag in v2.
Anyway, checking the output of
$ git grep -n -e '^[a-z]*\.[a-z]*[A-Z][A-Z][a-zA-Z]*::'
Documentation/config/
and comparing it with the output of
$ git grep -n -e '^[a-z]*\.[a-z]*[A-Z][a-zA-Z]*::'
Documentation/config/
I think we should spell "SSL" (which is an acronym) full in capital,
and possibly do the same for "CC", too.
Agreed about "SSL", which I also though about doing that way initially;
will change in v2. There are already instances of "SSL" being used,
such as in various http.proxySSL* configuration parameter names.
Though, "CC" should remain written as "Cc", because it's the way email
headers are capitalized, which "Cc" refers to.
