git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Dragan Simic <dsimic@manjaro.org>
Cc: git@vger.kernel.org
Subject: Re: [PATCH v3] documentation: send-email: use camel case consistently
Date: Tue, 20 Feb 2024 14:08:36 -0800	[thread overview]
Message-ID: <xmqq1q96okkb.fsf@gitster.g> (raw)
In-Reply-To: <877b5bec11caa8a328ee0d4f226fe0666fd35a10.1708466383.git.dsimic@manjaro.org> (Dragan Simic's message of "Tue, 20 Feb 2024 23:01:21 +0100")

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.






  reply	other threads:[~2024-02-20 22:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-20 22:01 [PATCH v3] documentation: send-email: use camel case consistently Dragan Simic
2024-02-20 22:08 ` Junio C Hamano [this message]
2024-02-20 22:17   ` Dragan Simic
2024-02-20 22:17 ` Kristoffer Haugsbakk
2024-02-20 22:21   ` Dragan Simic

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=xmqq1q96okkb.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=dsimic@manjaro.org \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).