From: Andrew Kreimer <algonell@gmail.com>
To: git@vger.kernel.org
Cc: Andrew Kreimer <algonell@gmail.com>
Subject: [PATCH 1/3] Documentation/technical: fix a typo
Date: Fri, 20 Sep 2024 11:28:13 +0300 [thread overview]
Message-ID: <20240920082815.8192-1-algonell@gmail.com> (raw)
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,
the number of folks who can test such a usecase is limited.
The primary reason to note the Behavior C usecase is that as we fix things
--
2.39.5
next reply other threads:[~2024-09-20 8:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-20 8:28 Andrew Kreimer [this message]
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
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=20240920082815.8192-1-algonell@gmail.com \
--to=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.