From: Eric Sunshine <sunshine@sunshineco.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Andrew Kreimer <algonell@gmail.com>, git@vger.kernel.org
Subject: Re: [PATCH 1/3] Documentation/technical: fix a typo
Date: Mon, 23 Sep 2024 13:32:03 -0400 [thread overview]
Message-ID: <CAPig+cSis+QYgkPM2pFrEpEWOyny3XpMJpgYbGbJu2ZL5SBmow@mail.gmail.com> (raw)
In-Reply-To: <xmqqbk0if5jv.fsf@gitster.g>
On Fri, Sep 20, 2024 at 4:12 PM Junio C Hamano <gitster@pobox.com> wrote:
> Andrew Kreimer <algonell@gmail.com> writes:
> > -Since there is no publically available VFS-related code for folks to try,
> > +Since there is no publicly available VFS-related code for folks to try,
>
> As a general rule, unless we are doing codewide sweep to use a
> single word in our glossary to refer to the same thing, or
> something, we should honor author's preference, when it is already
> written and it is not blatantly wrong.
>
> https://www.collinsdictionary.com/us/dictionary/english/publically
>
> I am inclined to say that we should keep it as written, but I am not
> a native speaker, so please cite a source that tells what is written
> is blatantly wrong to help me accept this patch.
For what it's worth, I am a native speaker, and I was taught that the
correct spelling is "publicly". Indeed, my Webster's dictionary from
that era lists only "publicly"; it does not mention "publically" at
all. The modern online Webster's still spells it "publicly", but at
least acknowledges "publically" by saying:
[variants] or less commonly "publically"
The modern day built-in macOS dictionary does not have an entry for
"publically" and goes out of its way to loudly proclaim (in bold in a
standout box) under its entry for "publicly":
USAGE: Note that the spelling is publicly, ending with the suffix
-ly, not publically.
The word "publicly" is, of course, so frequently misspelled that it is
not surprising that "publically" has been accepted into some
dictionaries as a legitimate spelling, but, as one who grew up
understanding the correct spelling to be "publicly", the variant
spelling still makes my reading hiccup big time, so I found no problem
with this patch.
next prev parent reply other threads:[~2024-09-23 17:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-20 8:28 [PATCH 1/3] Documentation/technical: fix a typo Andrew Kreimer
2024-09-20 8:28 ` [PATCH 2/3] Documentation/config: fix typos Andrew Kreimer
2024-09-20 8:28 ` [PATCH 3/3] Documentation: " Andrew Kreimer
2024-09-20 16:55 ` Eric Sunshine
2024-09-20 18:17 ` Junio C Hamano
2024-09-20 20:17 ` Junio C Hamano
2024-09-20 21:46 ` Andrew Kreimer
2024-09-20 20:12 ` [PATCH 1/3] Documentation/technical: fix a typo Junio C Hamano
2024-09-20 21:42 ` Andrew Kreimer
2024-09-23 17:32 ` Eric Sunshine [this message]
2024-09-23 18:55 ` Junio C Hamano
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=CAPig+cSis+QYgkPM2pFrEpEWOyny3XpMJpgYbGbJu2ZL5SBmow@mail.gmail.com \
--to=sunshine@sunshineco.com \
--cc=algonell@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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).