From: Tuomas Ahola Date: Thu, 18 Jun 2026 11:48:37 GMT Subject: Re: [PATCH] Fix typo in MaintNotes regarding versioning scheme Message-ID: <20260618114837.0_RVf%taahol@utu.fi> In-Reply-To: Junio C Hamano wrote: > Silas Poulson 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 --- MaintNotes | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) 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 . @@ -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