From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: v2.46.1? was Re: What's cooking in git.git (Aug 2024, #06; Fri, 16)
Date: Mon, 19 Aug 2024 18:49:07 +0200 (CEST) [thread overview]
Message-ID: <b6e3763d-945f-fdf7-e620-cd26b8c72419@gmx.de> (raw)
In-Reply-To: <xmqqwmkgjomp.fsf@gitster.g>
Hi Junio,
On Fri, 16 Aug 2024, Junio C Hamano wrote:
> 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
next prev parent reply other threads:[~2024-08-19 16:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-16 18:42 What's cooking in git.git (Aug 2024, #06; Fri, 16) Junio C Hamano
2024-08-19 16:49 ` Johannes Schindelin [this message]
2024-08-19 19:16 ` v2.46.1? was " Junio C Hamano
2024-08-20 20:15 ` Johannes Schindelin
2024-08-20 20:41 ` Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b6e3763d-945f-fdf7-e620-cd26b8c72419@gmx.de \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).