From: Andrew Kreimer <algonell@gmail.com>
To: git@vger.kernel.org
Cc: Andrew Kreimer <algonell@gmail.com>
Subject: [PATCH 2/3] Documentation/config: fix typos
Date: Fri, 20 Sep 2024 11:28:14 +0300 [thread overview]
Message-ID: <20240920082815.8192-2-algonell@gmail.com> (raw)
In-Reply-To: <20240920082815.8192-1-algonell@gmail.com>
Fix typos in documentation.
Signed-off-by: Andrew Kreimer <algonell@gmail.com>
---
Documentation/config/extensions.txt | 2 +-
Documentation/config/gc.txt | 2 +-
Documentation/config/remote.txt | 2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/Documentation/config/extensions.txt b/Documentation/config/extensions.txt
index 38dce3df35..f0a784447d 100644
--- a/Documentation/config/extensions.txt
+++ b/Documentation/config/extensions.txt
@@ -9,7 +9,7 @@ work and will produce hard-to-diagnose issues.
extensions.compatObjectFormat::
- Specify a compatitbility hash algorithm to use. The acceptable values
+ Specify a compatibility hash algorithm to use. The acceptable values
are `sha1` and `sha256`. The value specified must be different from the
value of extensions.objectFormat. This allows client level
interoperability between git repositories whose objectFormat matches
diff --git a/Documentation/config/gc.txt b/Documentation/config/gc.txt
index 1d4f9470ea..21d56db279 100644
--- a/Documentation/config/gc.txt
+++ b/Documentation/config/gc.txt
@@ -163,7 +163,7 @@ gc.repackFilterTo::
containing the filtered out objects. **WARNING:** The
specified location should be accessible, using for example the
Git alternates mechanism, otherwise the repo could be
- considered corrupt by Git as it migh not be able to access the
+ considered corrupt by Git as it might not be able to access the
objects in that packfile. See the `--filter-to=<dir>` option
of linkgit:git-repack[1] and the `objects/info/alternates`
section of linkgit:gitrepository-layout[5].
diff --git a/Documentation/config/remote.txt b/Documentation/config/remote.txt
index 36e771556c..71d1fee835 100644
--- a/Documentation/config/remote.txt
+++ b/Documentation/config/remote.txt
@@ -50,7 +50,7 @@ remote.<name>.skipFetchAll::
If true, this remote will be skipped when updating
using linkgit:git-fetch[1], the `update` subcommand of
linkgit:git-remote[1], and ignored by the prefetch task
- of `git maitenance`.
+ of `git maintenance`.
remote.<name>.receivepack::
The default program to execute on the remote side when pushing. See
--
2.39.5
next prev parent 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 [PATCH 1/3] Documentation/technical: fix a typo Andrew Kreimer
2024-09-20 8:28 ` Andrew Kreimer [this message]
2024-09-20 8:28 ` [PATCH 3/3] Documentation: fix typos 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-2-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.