git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Johannes Schindelin via GitGitGadget" <gitgitgadget@gmail.com>
To: git@vger.kernel.org
Cc: Johannes Schindelin <johannes.schindelin@gmx.de>,
	Johannes Schindelin <johannes.schindelin@gmx.de>
Subject: [PATCH] Fix a couple of typos in the v2.39.0 release notes
Date: Thu, 08 Dec 2022 14:48:07 +0000	[thread overview]
Message-ID: <pull.1442.git.1670510887255.gitgitgadget@gmail.com> (raw)

From: Johannes Schindelin <johannes.schindelin@gmx.de>

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
---
    Fix a couple of typos in the v2.39.0 release notes
    
    I cheated: I used VS Code's "Code Spell Checker" ;-)

Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-1442%2Fdscho%2Frelease-notes-typos-v1
Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-1442/dscho/release-notes-typos-v1
Pull-Request: https://github.com/gitgitgadget/git/pull/1442

 Documentation/RelNotes/2.39.0.txt | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/Documentation/RelNotes/2.39.0.txt b/Documentation/RelNotes/2.39.0.txt
index 3b8b0c010f9..1eb16534776 100644
--- a/Documentation/RelNotes/2.39.0.txt
+++ b/Documentation/RelNotes/2.39.0.txt
@@ -194,7 +194,7 @@ Fixes since v2.38
  * Force C locale while running tests around httpd to make sure we can
    find expected error messages in the log.
 
- * Fix a logic in "mailinfo -b" that miscomputed the length of a
+ * Fix a logic in "mailinfo -b" that mis-computed the length of a
    substring, which lead to an out-of-bounds access.
 
  * The codepath to sign learned to report errors when it fails to read
@@ -214,7 +214,7 @@ Fixes since v2.38
  * Clarify that "the sentence after <area>: prefix does not begin with
    a capital letter" rule applies only to the commit title.
 
- * "git branch --edit-description" on an unborh branch misleadingly
+ * "git branch --edit-description" on an unborn branch misleadingly
    said that no such branch exists, which has been corrected.
 
  * Work around older clang that warns against C99 zero initialization
@@ -264,7 +264,7 @@ Fixes since v2.38
 
  * "git diff --stat" etc. were invented back when everything was ASCII
    and strlen() was a way to measure the display width of a string;
-   adjust them to compute the display width assuming UTF-8 pathnames.
+   adjust them to compute the display width assuming UTF-8 path names.
    (merge ce8529b2bb tb/diffstat-with-utf8-strwidth later to maint).
 
  * "git branch --edit-description" can exit with status -1 which is
@@ -289,7 +289,7 @@ Fixes since v2.38
    option now implies --reapply-cherry-picks and --no-fork-point
    options.
 
- * The way "git repack" creared temporary files when it received a
+ * The way "git repack" created temporary files when it received a
    signal was prone to deadlocking, which has been corrected.
 
  * Various tests exercising the transfer.credentialsInUrl

base-commit: 2e71cbbddd64695d43383c25c7a054ac4ff86882
-- 
gitgitgadget

             reply	other threads:[~2022-12-08 14:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-08 14:48 Johannes Schindelin via GitGitGadget [this message]
2022-12-09  2:02 ` [PATCH] Fix a couple of typos in the v2.39.0 release notes 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=pull.1442.git.1670510887255.gitgitgadget@gmail.com \
    --to=gitgitgadget@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=johannes.schindelin@gmx.de \
    /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).