Re: [PATCH v3] documentation: send-email: use camel case consistently

From: Junio C Hamano <gitster@pobox.com>
Date: Feb 20, 2024, 22:08 UTC
Message-ID: <xmqq1q96okkb.fsf@gitster.g>
In-Reply-To: <877b5bec11caa8a328ee0d4f226fe0666fd35a10.1708466383.git.dsimic@manjaro.org>

Dragan Simic <dsimic@manjaro.org> writes:

> general rule for making abbreviations, with some exceptions.  For example,
> one rather well-known exception to this general rule is "SoC", which is the
> abbreviation for "system-on-chip". [2]

I am not opposed to say "we allow spelling 'carbon copy' as 'Cc' because too many people mistakenly use that capitalization pattern", which is what you earlier said, though. As I said, I do not insist one or the other capitalization, as long as it is backed by solid reasoning that would not confuse future developers.

It is very common to omit upcasing prepositions, articles, etc. when spelling acronyms in all capital, so "SoC" would not count as a good example of an exception. That's the kind of bogus justification of giving an exception to "Cc" I would rather want to avoid. It really is only "Cc" that needs to justify exception in your patch.