Git development
 help / color / mirror / Atom feed
From: Andrew Kreimer <algonell@gmail.com>
To: git@vger.kernel.org
Cc: Andrew Kreimer <algonell@gmail.com>
Subject: [PATCH v3] doc: fix typos via codespell
Date: Tue,  2 Jun 2026 14:15:18 +0300	[thread overview]
Message-ID: <20260602111552.6084-1-algonell@gmail.com> (raw)
In-Reply-To: <20260506101631.18127-1-algonell@gmail.com>

There are some typos in the documentation, comments, etc.
Fix them via codespell.

Signed-off-by: Andrew Kreimer <algonell@gmail.com>
---
v3:
  - Address test breaking changes (strings bounded by single quotes).
  - Thank you for your patience (extreme noise/gain ratio).

 t/t1700-split-index.sh         | 2 +-
 t/t3909-stash-pathspec-file.sh | 6 +++---
 2 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/t/t1700-split-index.sh b/t/t1700-split-index.sh
index 869fb4a14e..887e72a5fa 100755
--- a/t/t1700-split-index.sh
+++ b/t/t1700-split-index.sh
@@ -502,7 +502,7 @@ test_expect_success 'do not refresh null base index' '
 		git checkout main &&
 		git update-index --split-index &&
 		test_commit more &&
-		# must not write a new shareindex, or we won't catch the problem
+		# must not write a new shareindex, or we will not catch the problem
 		git -c splitIndex.maxPercentChange=100 merge --no-edit side-branch 2>err &&
 		# i.e. do not expect warnings like
 		# could not freshen shared index .../shareindex.00000...
diff --git a/t/t3909-stash-pathspec-file.sh b/t/t3909-stash-pathspec-file.sh
index 3afa6bff3d..e34cea6ce1 100755
--- a/t/t3909-stash-pathspec-file.sh
+++ b/t/t3909-stash-pathspec-file.sh
@@ -29,7 +29,7 @@ verify_expect () {
 test_expect_success 'simplest' '
 	restore_checkpoint &&
 
-	# More files are written to make sure that git didn't ignore
+	# More files are written to make sure that git did not ignore
 	# --pathspec-from-file, stashing everything
 	echo A >fileA.t &&
 	echo B >fileB.t &&
@@ -47,7 +47,7 @@ test_expect_success 'simplest' '
 test_expect_success '--pathspec-file-nul' '
 	restore_checkpoint &&
 
-	# More files are written to make sure that git didn't ignore
+	# More files are written to make sure that git did not ignore
 	# --pathspec-from-file, stashing everything
 	echo A >fileA.t &&
 	echo B >fileB.t &&
@@ -66,7 +66,7 @@ test_expect_success '--pathspec-file-nul' '
 test_expect_success 'only touches what was listed' '
 	restore_checkpoint &&
 
-	# More files are written to make sure that git didn't ignore
+	# More files are written to make sure that git did not ignore
 	# --pathspec-from-file, stashing everything
 	echo A >fileA.t &&
 	echo B >fileB.t &&

Interdiff against v2:
  diff --git a/t/t1700-split-index.sh b/t/t1700-split-index.sh
  index 869fb4a14e..887e72a5fa 100755
  --- a/t/t1700-split-index.sh
  +++ b/t/t1700-split-index.sh
  @@ -502,7 +502,7 @@ test_expect_success 'do not refresh null base index' '
   		git checkout main &&
   		git update-index --split-index &&
   		test_commit more &&
  -		# must not write a new shareindex, or we won't catch the problem
  +		# must not write a new shareindex, or we will not catch the problem
   		git -c splitIndex.maxPercentChange=100 merge --no-edit side-branch 2>err &&
   		# i.e. do not expect warnings like
   		# could not freshen shared index .../shareindex.00000...
  diff --git a/t/t3909-stash-pathspec-file.sh b/t/t3909-stash-pathspec-file.sh
  index 3afa6bff3d..e34cea6ce1 100755
  --- a/t/t3909-stash-pathspec-file.sh
  +++ b/t/t3909-stash-pathspec-file.sh
  @@ -29,7 +29,7 @@ verify_expect () {
   test_expect_success 'simplest' '
   	restore_checkpoint &&
   
  -	# More files are written to make sure that git didn't ignore
  +	# More files are written to make sure that git did not ignore
   	# --pathspec-from-file, stashing everything
   	echo A >fileA.t &&
   	echo B >fileB.t &&
  @@ -47,7 +47,7 @@ test_expect_success 'simplest' '
   test_expect_success '--pathspec-file-nul' '
   	restore_checkpoint &&
   
  -	# More files are written to make sure that git didn't ignore
  +	# More files are written to make sure that git did not ignore
   	# --pathspec-from-file, stashing everything
   	echo A >fileA.t &&
   	echo B >fileB.t &&
  @@ -66,7 +66,7 @@ test_expect_success '--pathspec-file-nul' '
   test_expect_success 'only touches what was listed' '
   	restore_checkpoint &&
   
  -	# More files are written to make sure that git didn't ignore
  +	# More files are written to make sure that git did not ignore
   	# --pathspec-from-file, stashing everything
   	echo A >fileA.t &&
   	echo B >fileB.t &&

Range-diff against v2:
-:  ---------- > 1:  bcbd09129a doc: fix typos via codespell
-- 
2.54.0


  parent reply	other threads:[~2026-06-02 11:15 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-06 10:15 [PATCH] doc: fix typos via codespell Andrew Kreimer
2026-05-09 22:14 ` Kristoffer Haugsbakk
2026-05-28 17:53   ` Kristoffer Haugsbakk
2026-05-28 20:37     ` Junio C Hamano
2026-05-10 22:21 ` Junio C Hamano
2026-05-23 17:24   ` Weijie Yuan
2026-05-29  8:17     ` [PATCH] docs: fix typos and grammar Weijie Yuan
2026-06-01 22:23       ` Junio C Hamano
2026-06-02  5:58         ` Weijie Yuan
2026-06-02  6:12           ` Weijie Yuan
2026-05-31 18:43 ` [PATCH v2] doc: fix typos via codespell Andrew Kreimer
2026-06-01  1:16   ` Junio C Hamano
2026-06-01 20:59     ` Kristoffer Haugsbakk
2026-06-02 11:15 ` Andrew Kreimer [this message]
2026-06-02 13:57   ` [PATCH v3] " 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=20260602111552.6084-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox