From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Aug 2023, #06; Fri, 18)
Date: Sat, 19 Aug 2023 20:03:16 -0400 [thread overview]
Message-ID: <20230820000316.GA601058@coredump.intra.peff.net> (raw)
In-Reply-To: <xmqq8ra7u5jn.fsf@gitster.g>
On Fri, Aug 18, 2023 at 07:31:08PM -0700, Junio C Hamano wrote:
> Git 2.42 will be released early next week.
Since the release is soon, I just wanted to call your attention to:
https://lore.kernel.org/git/20230819235342.GA600744@coredump.intra.peff.net/
which fixes a very minor regression. It's small enough that I suspect
nobody would even notice, but the fix is small and obvious enough that
it is probably OK to apply between -rc2 and the release.
-Peff
prev parent reply other threads:[~2023-08-20 0:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-19 2:31 What's cooking in git.git (Aug 2023, #06; Fri, 18) Junio C Hamano
2023-08-20 0:03 ` Jeff King [this message]
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=20230820000316.GA601058@coredump.intra.peff.net \
--to=peff@peff.net \
--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).