{"thread":{"id":"65041","subject":"[PATCH] Fix typo in MaintNotes regarding versioning scheme","startedAt":"2026-02-22T15:39:33Z","lastAt":"2026-10-01T10:18:41Z","messageCount":6,"participants":["Silas via GitGitGadget","Silas Poulson","Junio C Hamano","Tuomas Ahola"],"isPatch":true,"patchVersion":1,"patchTotal":null},"messages":[{"id":"536647","messageId":"pull.2209.git.git.1771774770368.gitgitgadget@gmail.com","threadId":"65041","inReplyTo":null,"subject":"[PATCH] Fix typo in MaintNotes regarding versioning scheme","fromName":"Silas via GitGitGadget","fromEmail":"gitgitgadget@gmail.com","sentAt":"2026-02-22T15:39:30Z","receivedAt":"2026-02-22T15:39:33Z","isPatch":true,"body":"From: Silas \n\nCorrected a typo in the versioning scheme description.\n\nSigned-off-by: bear8642 \n---\n Fix typo in MaintNotes regarding versioning scheme\n\nPublished-As: https://github.com/gitgitgadget/git/releases/tag/pr-git-2209%2Fbear8642%2Fpatch-1-v1\nFetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-git-2209/bear8642/patch-1-v1\nPull-Request: https://github.com/git/git/pull/2209\n\n MaintNotes | 2 +-\n 1 file changed, 1 insertion(+), 1 deletion(-)\n\ndiff --git a/MaintNotes b/MaintNotes\nindex 12ba677c36..399d74807e 100644\n--- a/MaintNotes\n+++ b/MaintNotes\n@@ -183,7 +183,7 @@ ready to be used in a production setting. Every now and then, a\n \"feature release\" is cut from the tip of this branch. They used to be\n named with three dotted decimal digits (e.g., \"1.8.5\"), but we have\n switched the versioning scheme and \"feature releases\" are named with\n-ttwo-dotted decimal digits (e.g. \"2.53\"), whose tag ends with \".0\"\n+two-dotted decimal digits (e.g. \"2.53\"), whose tag ends with \".0\"\n (e.g., \"v2.53.0\").\n \n The last such release was Git 2.53, made on Feb 2nd, 2026. We aim to\n\nbase-commit: 0ceb40560a5cca1c98c1d1b37a1f3254fbdd2efd\n-- \ngitgitgadget\n"},{"id":"538087","messageId":"882432fe-30f5-46c5-9efa-5b8a047283b6@dyalog.com","threadId":"65041","inReplyTo":"pull.2209.git.git.1771774770368.gitgitgadget@gmail.com","subject":"Re: [PATCH] Fix typo in MaintNotes regarding versioning scheme","fromName":"Silas Poulson","fromEmail":"silas@dyalog.com","sentAt":"2026-03-06T15:14:14Z","receivedAt":"2026-03-06T15:23:42Z","isPatch":true,"body":"Bump\n\nI'm aware this is a very minor change, but it would be good to not let \nthis fall through the cracks.\n\nThanks,\nSilas\n"},{"id":"538114","messageId":"xmqqfr6czmye.fsf@gitster.g","threadId":"65041","inReplyTo":"882432fe-30f5-46c5-9efa-5b8a047283b6@dyalog.com","subject":"Re: [PATCH] Fix typo in MaintNotes regarding versioning scheme","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2026-03-06T21:07:21Z","receivedAt":"2026-03-06T21:07:24Z","isPatch":true,"body":"Silas Poulson writes:\n\n> I'm aware this is a very minor change, but it would be good to not let \n> this fall through the cracks.\n\nThanks for noticing a typo.\n\nWill update before the next issue is sent to the mailing list. No\npoint in changing it before that.\n"},{"id":"545835","messageId":"20260618114837.0_RVf%taahol@utu.fi","threadId":"65041","inReplyTo":"xmqqfr6czmye.fsf@gitster.g","subject":"Re: [PATCH] Fix typo in MaintNotes regarding versioning scheme","fromName":"Tuomas Ahola","fromEmail":"taahol@utu.fi","sentAt":"2026-06-18T11:48:37Z","receivedAt":"2026-06-18T11:48:51Z","isPatch":true,"body":"Junio C Hamano wrote:\n\n> Silas Poulson writes:\n> \n> > I'm aware this is a very minor change, but it would be good to not let \n> > this fall through the cracks.\n> \n> Thanks for noticing a typo.\n> \n> Will update before the next issue is sent to the mailing list. No\n> point in changing it before that.\n\nOn that occasion, please consider also these fixes:\n-----8<-----\nSubject: [PATCH] MaintNotes: fix typos and grammar\n\nSigned-off-by: Tuomas Ahola \n---\n MaintNotes | 10 +++++-----\n 1 file changed, 5 insertions(+), 5 deletions(-)\n\ndiff --git a/MaintNotes b/MaintNotes\nindex 12ba677c36..44b29c9e10 100644\n--- a/MaintNotes\n+++ b/MaintNotes\n@@ -82,7 +82,7 @@ available at:\n There is a volunteer-run newsletter to serve our community (\"Git Rev\n News\" https://git.github.io/rev_news/).\n \n-Git is a member project of software freedom conservancy, a non-profit\n+Git is a member project of Software Freedom Conservancy, a non-profit\n organization (https://sfconservancy.org/). To reach a committee of\n liaisons to the conservancy, contact them at .\n \n@@ -245,7 +245,7 @@ by others may cause conflicts with their own work, and find people who\n are working on these topics to talk to before the potential conflicts\n get out of control. It would be a good idea to fork your work from\n maint or master and to (1) test it by itself, (2) test a temporary\n-merge of it to \"next\" and (3) test a temporary merge to it to \"seen\",\n+merge of it to \"next\" and (3) test a temporary merge of it to \"seen\",\n before sending it to the list (or asking GitGitGadget to send it to\n the list).\n \n@@ -262,10 +262,10 @@ using the topics that didn't make the cut in the feature release.\n Some topics that used to be in \"next\" during the previous cycle may\n get ejected from \"next\" when this happens.\n \n-A natural consequence of how \"next\" and \"seen\" bundles topics together\n-is that until a topic is merged to \"next\", updates to it is expected\n+A natural consequence of how \"next\" and \"seen\" bundle topics together\n+is that until a topic is merged to \"next\", updates to it are expected\n by replacing the patch(es) in the topic with an improved version, and\n-once a topic is merged to \"next\", updates to it needs to come as\n+once a topic is merged to \"next\", updates to it need to come as\n incremental patches, pointing out what was wrong in the previous\n patches and how the problem was corrected. The idea is that if many\n reviewers thought it has seen enough eyeballs and is good enough for\n\nbase-commit: f9b08c9b285c9154e41b9f5fce7506018b83dfcb\n-- \n2.30.2\n\n"},{"id":"545856","messageId":"xmqq1pe3ubr0.fsf@gitster.g","threadId":"65041","inReplyTo":"20260618114837.0_RVf%taahol@utu.fi","subject":"Re: [PATCH] Fix typo in MaintNotes regarding versioning scheme","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2026-06-18T15:08:51Z","receivedAt":"2026-06-18T15:08:53Z","isPatch":true,"body":"Tuomas Ahola writes:\n\n> Junio C Hamano wrote:\n>\n>> Silas Poulson writes:\n>> \n>> > I'm aware this is a very minor change, but it would be good to not let \n>> > this fall through the cracks.\n>> \n>> Thanks for noticing a typo.\n>> \n>> Will update before the next issue is sent to the mailing list. No\n>> point in changing it before that.\n>\n> On that occasion, please consider also these fixes:\n\nThanks. Will squash in. The next issue of Maintotes will come\nright after 2.55 final gets tagged, so we have a bit more time.\n\n\n"},{"id":"553828","messageId":"20261001101828.pe12F%taahol@utu.fi","threadId":"65041","inReplyTo":"xmqq1pe3ubr0.fsf@gitster.g","subject":"Re: [PATCH] Fix typo in MaintNotes regarding versioning scheme","fromName":"Tuomas Ahola","fromEmail":"taahol@utu.fi","sentAt":"2026-10-01T10:18:28Z","receivedAt":"2026-10-01T10:18:41Z","isPatch":true,"body":"Junio C Hamano wrote:\n\n> Tuomas Ahola writes:\n> \n> > Junio C Hamano wrote:\n> >\n> >> Silas Poulson writes:\n> >> \n> >> > I'm aware this is a very minor change, but it would be good to not let \n> >> > this fall through the cracks.\n> >> \n> >> Thanks for noticing a typo.\n> >> \n> >> Will update before the next issue is sent to the mailing list. No\n> >> point in changing it before that.\n> >\n> > On that occasion, please consider also these fixes:\n> \n> Thanks. Will squash in. The next issue of Maintotes will come\n> right after 2.55 final gets tagged, so we have a bit more time.\n> \n> \n\n...ping?\n\nIt's not yet too late for the 2.56 MaintNotes issue if we want to continue\nhaving those.\n"}]}