git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[PATCH] Fix typo in MaintNotes regarding versioning scheme

From
SGSilas via GitGitGadget <gitgitgadget@gmail.com>
Date
Feb 22, 2026, 15:39 UTC
Message-ID
<pull.2209.git.git.1771774770368.gitgitgadget@gmail.com>
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: Silas Poulson
Message 1 of 6 in “Fix typo in MaintNotes regarding versioning scheme”
  1. Fix typo in MaintNotes regarding versioning schemeSilas via GitGitGadget, Feb 22, 2026
  2. Silas PoulsonMar 6, 2026
  3. Junio C HamanoMar 6, 2026
  4. Tuomas AholaJun 18, 2026
  5. Junio C HamanoJun 18, 2026
  6. Tuomas AholaOct 1, 2026

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.