Description
This obviously does not have to be part of this miniseries, but I
wonder if we should have a list of all the configuration variables
in one place that we can use to record the canonical spelling of
these variables. As$ git grep -h -E -i
-e '^[a-z][-a-z0-9].[a-z][-a-z0-9]::'
-e '^[a-z][-a-z0-9].(*|<?[a-z][-a-z0-9]>?).(*|<?[a-z][-a-z0-9]*>?)::'
Documentation/configgives many hits with camelCased names, it might be a good place to
start.Pretending that the above gives a good "canonical list" (it does not
yet, if you look at the hits), I got curious how far we can go.Massaging the output from the above into config-variables.lst
$ ... above command ... |
sed -e 's/::$//' |
sort -u >config-variables.lstand then to extract use of these tokens in the main part of the
documentation like this:$ git grep -h -o -i -F -f config-variables.lst --
Documentation/ ':!Documentation/RelNotes/' |
sort -u >config-usage.lstgives us something we can compare with the "canonical" usage list.
$ comm -3 config-usage.lst config-variables.lst
blame.blankboundary
core.excludesfile
core.filemode
core.gitproxy
core.ignorestat
core.logallrefupdates
core.repositoryformatversion
core.trustCtime
http.sslverify
http.sslversion
i18n.commitencoding
push.pushoption
remote..partialCloneFilter
remote.pushdefault
repack.UseDeltaBaseOffset
sendemail.aliasesfile
showbranch.default
transfer.hiderefs
uploadArchive.allowUnreachableSome of them may be false hits, some may be showing that the copy in
Documentation/config/ are spelled in all lowercase, but the majority
of the hits above seem to be genuine errors similar to what you fixed
in your patch.Thanks.