From: Junio C Hamano <gitster@pobox.com>
To: Andrew Kreimer <algonell@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 1/3] Documentation/technical: fix a typo
Date: Fri, 20 Sep 2024 13:12:20 -0700 [thread overview]
Message-ID: <xmqqbk0if5jv.fsf@gitster.g> (raw)
In-Reply-To: <20240920082815.8192-1-algonell@gmail.com> (Andrew Kreimer's message of "Fri, 20 Sep 2024 11:28:13 +0300")
Andrew Kreimer <algonell@gmail.com> writes:
> Fix a typo in documentation.
>
> Signed-off-by: Andrew Kreimer <algonell@gmail.com>
> ---
> Documentation/technical/sparse-checkout.txt | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/technical/sparse-checkout.txt b/Documentation/technical/sparse-checkout.txt
> index fa0d01cbda..d968659354 100644
> --- a/Documentation/technical/sparse-checkout.txt
> +++ b/Documentation/technical/sparse-checkout.txt
> @@ -287,7 +287,7 @@ everything behaves like a dense checkout with a few exceptions (e.g. branch
> checkouts and switches write fewer things, knowing the VFS will lazily
> write the rest on an as-needed basis).
>
> -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.
Thanks.
next prev parent reply other threads:[~2024-09-20 20:12 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 ` Junio C Hamano [this message]
2024-09-20 21:42 ` [PATCH 1/3] Documentation/technical: fix a typo Andrew Kreimer
2024-09-23 17:32 ` Eric Sunshine
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=xmqqbk0if5jv.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=algonell@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.