All of lore.kernel.org
 help / color / mirror / Atom feed
From: Taylor Blau <me@ttaylorr.com>
To: git@vger.kernel.org
Cc: gitster@pobox.com
Subject: [PATCH] Documentation/RelNotes: fix a typo in 2.36's relnotes
Date: Wed, 13 Apr 2022 17:03:28 -0400	[thread overview]
Message-ID: <d23e51b8dc78651dbd751473c0f8b3dcd6bc3ac6.1649883760.git.me@ttaylorr.com> (raw)

Signed-off-by: Taylor Blau <me@ttaylorr.com>
---
Noticed while reading the RelNotes for GitHub's release highlights blog
post.

I'm pretty sure that this is a typo for "not-so-uncommon", but I could
be wrong (in which case, feel free to drop this patch on the floor).

 Documentation/RelNotes/2.36.0.txt | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Documentation/RelNotes/2.36.0.txt b/Documentation/RelNotes/2.36.0.txt
index d61ade21e2..98e1c97617 100644
--- a/Documentation/RelNotes/2.36.0.txt
+++ b/Documentation/RelNotes/2.36.0.txt
@@ -46,7 +46,7 @@ UI, Workflows & Features

  * "git branch" learned the "--recurse-submodules" option.

- * A not-so-common mistake is to write a script to feed "git bisect
+ * A not-so-uncommon mistake is to write a script to feed "git bisect
    run" without making it executable, in which case all tests will
    exit with 126 or 127 error codes, even on revisions that are marked
    as good.  Try to recognize this situation and stop iteration early.
--
2.35.1.73.gccc5557600

             reply	other threads:[~2022-04-13 21:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-13 21:03 Taylor Blau [this message]
2022-04-13 21:13 ` [PATCH] Documentation/RelNotes: fix a typo in 2.36's relnotes Junio C Hamano
2022-04-13 21:46   ` Taylor Blau

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=d23e51b8dc78651dbd751473c0f8b3dcd6bc3ac6.1649883760.git.me@ttaylorr.com \
    --to=me@ttaylorr.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    /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.