v2.46.1? was Re: What's cooking in git.git (Aug 2024, #06; Fri, 16)

From: Johannes Schindelin <johannes.schindelin@gmx.de>
Date: Aug 19, 2024, 16:49 UTC
Message-ID: <b6e3763d-945f-fdf7-e620-cd26b8c72419@gmx.de>
In-Reply-To: <xmqqwmkgjomp.fsf@gitster.g>

Hi Junio,

On Fri, 16 Aug 2024, Junio C Hamano wrote:

Show 13 quoted lines

> Here are the topics that have been cooking in my tree.  Commits
> prefixed with '+' are in 'next' (being in 'next' is a sign that a
> topic is stable enough to be used and are candidate to be in a
> future release).  Commits prefixed with '-' are only in 'seen', and
> aren't considered "accepted" at all and may be annotated with an URL
> to a message that raises issues but they are no means exhaustive.  A
> topic without enough support may be discarded after a long period of
> no activity (of course they can be resubmit when new interests
> arise).
>
> Copies of the source code to Git live in many repositories, and the
> following is a list of the ones I push into or their mirrors.  Some
> repositories have only a subset of branches.

I frequently look at these two paragraphs in the What's cooking mails, or more specifically: at a paragraph inserted between these two occasionally, to get hints about imminent maintenance versions (to allow me to better prepare for them such as keeping back component updates in Git for Windows that strike me as needing some exercise before being released in an official version).

About 2.5h after sending the quoted mail, it seems that the `maint` branch was updated with a hint that you plan on releasing a v2.46.1.

Could I ask you what your plans are regarding v2.46.1 so that I don't exercise my weak fortune-telling abilities that would shock Sybill Trelawney?

Thank you, Johannes