threads / patch / 65041

patchFix typo in MaintNotes regarding versioning scheme

Subject: [PATCH] Fix typo in MaintNotes regarding versioning scheme

## tl;dr

6 messages between Feb 22, 2026 and Oct 1, 2026. Diffs are folded; open one to read it.

replies: 5people: 4as markdown or json

Silas via GitGitGadget· Feb 22, 2026, 15:39 UTC · lore
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(-)
Show changes to MaintNotes +1 −1
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
Junio C Hamano· Mar 6, 2026, 21:07 UTC · re: Silas Poulson · lore

Re: [PATCH] Fix typo in MaintNotes regarding versioning scheme

Silas Poulson <silas@dyalog.com> writes:
> I'm aware this is a very minor change, but it would be good to not let 
> this fall through the cracks.
Thanks for noticing a typo.

Will update before the next issue is sent to the mailing list. No point in changing it before that.

Tuomas Ahola· Jun 18, 2026, 11:48 UTC · re: Junio C Hamano · lore

Re: [PATCH] Fix typo in MaintNotes regarding versioning scheme

Junio C Hamano <gitster@pobox.com> wrote:
Show 9 quoted lines
> Silas Poulson <silas@dyalog.com> writes:
> 
> > I'm aware this is a very minor change, but it would be good to not let 
> > this fall through the cracks.
> 
> Thanks for noticing a typo.
> 
> Will update before the next issue is sent to the mailing list.  No
> point in changing it before that.
On that occasion, please consider also these fixes:
-----8<-----
Subject: [PATCH] MaintNotes: fix typos and grammar
Signed-off-by: Tuomas Ahola <taahol@utu.fi>
---
 MaintNotes | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)
Show changes to MaintNotes +5 −5
diff --git a/MaintNotes b/MaintNotes
index 12ba677c36..44b29c9e10 100644
--- a/MaintNotes
+++ b/MaintNotes
@@ -82,7 +82,7 @@ available at:
 There is a volunteer-run newsletter to serve our community ("Git Rev
 News" https://git.github.io/rev_news/).
 
-Git is a member project of software freedom conservancy, a non-profit
+Git is a member project of Software Freedom Conservancy, a non-profit
 organization (https://sfconservancy.org/).  To reach a committee of
 liaisons to the conservancy, contact them at <git@sfconservancy.org>.
 
@@ -245,7 +245,7 @@ by others may cause conflicts with their own work, and find people who
 are working on these topics to talk to before the potential conflicts
 get out of control.  It would be a good idea to fork your work from
 maint or master and to (1) test it by itself, (2) test a temporary
-merge of it to "next" and (3) test a temporary merge to it to "seen",
+merge of it to "next" and (3) test a temporary merge of it to "seen",
 before sending it to the list (or asking GitGitGadget to send it to
 the list).
 
@@ -262,10 +262,10 @@ using the topics that didn't make the cut in the feature release.
 Some topics that used to be in "next" during the previous cycle may
 get ejected from "next" when this happens.
 
-A natural consequence of how "next" and "seen" bundles topics together
-is that until a topic is merged to "next", updates to it is expected
+A natural consequence of how "next" and "seen" bundle topics together
+is that until a topic is merged to "next", updates to it are expected
 by replacing the patch(es) in the topic with an improved version, and
-once a topic is merged to "next", updates to it needs to come as
+once a topic is merged to "next", updates to it need to come as
 incremental patches, pointing out what was wrong in the previous
 patches and how the problem was corrected.  The idea is that if many
 reviewers thought it has seen enough eyeballs and is good enough for

base-commit: f9b08c9b285c9154e41b9f5fce7506018b83dfcb
-- 
2.30.2
Junio C Hamano· Jun 18, 2026, 15:08 UTC · re: Tuomas Ahola · lore

Re: [PATCH] Fix typo in MaintNotes regarding versioning scheme

Tuomas Ahola <taahol@utu.fi> writes:
Show 13 quoted lines
> Junio C Hamano <gitster@pobox.com> wrote:
>
>> Silas Poulson <silas@dyalog.com> writes:
>> 
>> > I'm aware this is a very minor change, but it would be good to not let 
>> > this fall through the cracks.
>> 
>> Thanks for noticing a typo.
>> 
>> Will update before the next issue is sent to the mailing list.  No
>> point in changing it before that.
>
> On that occasion, please consider also these fixes:

Thanks. Will squash in. The next issue of Maintotes will come right after 2.55 final gets tagged, so we have a bit more time.

Tuomas Ahola· Oct 1, 2026, 10:18 UTC · re: Junio C Hamano · lore

Re: [PATCH] Fix typo in MaintNotes regarding versioning scheme

Junio C Hamano <gitster@pobox.com> wrote:
Show 20 quoted lines
> Tuomas Ahola <taahol@utu.fi> writes:
> 
> > Junio C Hamano <gitster@pobox.com> wrote:
> >
> >> Silas Poulson <silas@dyalog.com> writes:
> >> 
> >> > I'm aware this is a very minor change, but it would be good to not let 
> >> > this fall through the cracks.
> >> 
> >> Thanks for noticing a typo.
> >> 
> >> Will update before the next issue is sent to the mailing list.  No
> >> point in changing it before that.
> >
> > On that occasion, please consider also these fixes:
> 
> Thanks.  Will squash in.  The next issue of Maintotes will come
> right after 2.55 final gets tagged, so we have a bit more time.
> 
> 
...ping?

It's not yet too late for the 2.56 MaintNotes issue if we want to continue having those.

← back to recent threads