From: Junio C Hamano <gitster@pobox.com>
To: Eric Sunshine <sunshine@sunshineco.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 11:55:15 -0700 [thread overview]
Message-ID: <xmqq34lq2oa4.fsf@gitster.g> (raw)
In-Reply-To: <CAPig+cSis+QYgkPM2pFrEpEWOyny3XpMJpgYbGbJu2ZL5SBmow@mail.gmail.com> (Eric Sunshine's message of "Mon, 23 Sep 2024 13:32:03 -0400")
Eric Sunshine <sunshine@sunshineco.com> writes:
> 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.
Yup, living languages annoy old-timers more than new folks with
phrases and usages that used to be ungrammatical gaining legitimacy
with wider use. I see this all the time in the language I am native
in, too.
Thanks for an input. Let's queue this patch, then.
prev parent reply other threads:[~2024-09-23 18:55 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
2024-09-23 18:55 ` Junio C Hamano [this message]
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=xmqq34lq2oa4.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=algonell@gmail.com \
--cc=git@vger.kernel.org \
--cc=sunshine@sunshineco.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).