From: <rsbecker@nexbridge.com>
To: "'Junio C Hamano'" <gitster@pobox.com>, <git@vger.kernel.org>
Cc: <git-packagers@googlegroups.com>
Subject: RE: [ANNOUNCE] Git v2.46.1
Date: Sat, 14 Sep 2024 21:16:08 -0400 [thread overview]
Message-ID: <023601db070c$db740f60$925c2e20$@nexbridge.com> (raw)
In-Reply-To: <xmqqikuytbxd.fsf@gitster.g>
On September 14, 2024 12:53 PM, Junio C Hamano wrote:
>To: git@vger.kernel.org
>Cc: Linux Kernel <linux-kernel@vger.kernel.org>; git-packagers@googlegroups.com
>Subject: [ANNOUNCE] Git v2.46.1
>
>The latest maintenance release Git v2.46.1 is now available at the usual places.
>Unlike maintenance releases in the recent past, this one is _not_ about security
>fixes, but primarily about fixes to various commands that can work outside a
>repository barfing due to lack of initialization of the hash function. IOW, it is not the
>end of the world if you did not update to this version for a few weeks, or wait for
>2.47 ;-).
Successfully deployed for NonStop x86 and ia64. Thank you, team, for all your efforts.
--Randall
prev parent reply other threads:[~2024-09-15 1:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-14 16:52 [ANNOUNCE] Git v2.46.1 Junio C Hamano
2024-09-15 1:16 ` rsbecker [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='023601db070c$db740f60$925c2e20$@nexbridge.com' \
--to=rsbecker@nexbridge.com \
--cc=git-packagers@googlegroups.com \
--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