From: "Ophir Bleicher via GitGitGadget" <gitgitgadget@gmail.com>
To: git@vger.kernel.org
Cc: Ophir Bleicher <ophirble@gmail.com>, Ophir Bleicher <ophirble@gmail.com>
Subject: [PATCH] doc: correct typo in 2.46.0.adoc
Date: Fri, 20 Nov 2026 12:23:18 +0000 [thread overview]
Message-ID: <pull.2493.git.git.1795177398801.gitgitgadget@gmail.com> (raw)
From: Ophir Bleicher <ophirble@gmail.com>
Fixed typo in the 'git describe --dirty --broken' section of the
release notes (chang -> change).
Signed-off-by: Ophir Bleicher <ophirble@gmail.com>
---
doc: correct typo in 2.46.0.adoc
Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-git-2493%2FOphirBleicher%2Fpatch-1-v1
Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-git-2493/OphirBleicher/patch-1-v1
Pull-Request: https://github.com/git/git/pull/2493
Documentation/RelNotes/2.46.0.adoc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/RelNotes/2.46.0.adoc b/Documentation/RelNotes/2.46.0.adoc
index c06a04a91b..2d7b7a0bc5 100644
--- a/Documentation/RelNotes/2.46.0.adoc
+++ b/Documentation/RelNotes/2.46.0.adoc
@@ -406,7 +406,7 @@ Fixes since v2.45
(merge 4b837f821e rs/simplify-submodule-helper-super-prefix-invocation later to maint).
* "git describe --dirty --broken" forgot to refresh the index before
- seeing if there is any chang, ("git describe --dirty" correctly did
+ seeing if there is any change, ("git describe --dirty" correctly did
so), which has been corrected.
(merge b8ae42e292 as/describe-broken-refresh-index-fix later to maint).
base-commit: f7de81456940dd6f3274e461149bba12965de609
--
gitgitgadget
next reply other threads:[~2026-11-20 12:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-20 12:23 Ophir Bleicher via GitGitGadget [this message]
2026-11-20 19:00 ` [PATCH v2] doc: correct typo in 2.46.0.adoc Ophir Bleicher via GitGitGadget
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.2493.git.git.1795177398801.gitgitgadget@gmail.com \
--to=gitgitgadget@gmail.com \
--cc=git@vger.kernel.org \
--cc=ophirble@gmail.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.