From: "Silas via GitGitGadget" <gitgitgadget@gmail.com>
To: git@vger.kernel.org
Cc: Silas <silas@dyalog.com>, Silas <silas@dyalog.com>
Subject: [PATCH] Fix typo in MaintNotes regarding versioning scheme
Date: Sun, 22 Feb 2026 15:39:30 +0000 [thread overview]
Message-ID: <pull.2209.git.git.1771774770368.gitgitgadget@gmail.com> (raw)
From: Silas <silas@dyalog.com>
Corrected a typo in the versioning scheme description.
Signed-off-by: bear8642 <silas@dyalog.com>
---
Fix typo in MaintNotes regarding versioning scheme
Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-git-2209%2Fbear8642%2Fpatch-1-v1
Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-git-2209/bear8642/patch-1-v1
Pull-Request: https://github.com/git/git/pull/2209
MaintNotes | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/MaintNotes b/MaintNotes
index 12ba677c36..399d74807e 100644
--- a/MaintNotes
+++ b/MaintNotes
@@ -183,7 +183,7 @@ ready to be used in a production setting. Every now and then, a
"feature release" is cut from the tip of this branch. They used to be
named with three dotted decimal digits (e.g., "1.8.5"), but we have
switched the versioning scheme and "feature releases" are named with
-ttwo-dotted decimal digits (e.g. "2.53"), whose tag ends with ".0"
+two-dotted decimal digits (e.g. "2.53"), whose tag ends with ".0"
(e.g., "v2.53.0").
The last such release was Git 2.53, made on Feb 2nd, 2026. We aim to
base-commit: 0ceb40560a5cca1c98c1d1b37a1f3254fbdd2efd
--
gitgitgadget
next reply other threads:[~2026-02-22 15:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-22 15:39 Silas via GitGitGadget [this message]
2026-03-06 15:14 ` [PATCH] Fix typo in MaintNotes regarding versioning scheme Silas Poulson
2026-03-06 21:07 ` 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.2209.git.git.1771774770368.gitgitgadget@gmail.com \
--to=gitgitgadget@gmail.com \
--cc=git@vger.kernel.org \
--cc=silas@dyalog.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox