From: <rsbecker@nexbridge.com>
To: "'Junio C Hamano'" <gitster@pobox.com>, <git@vger.kernel.org>
Cc: "'Linux Kernel'" <linux-kernel@vger.kernel.org>,
<git-packagers@googlegroups.com>
Subject: RE: [ANNOUNCE] Git v2.49.0-rc1
Date: Tue, 4 Mar 2025 20:05:31 -0500 [thread overview]
Message-ID: <001e01db8d6a$b4480470$1cd80d50$@nexbridge.com> (raw)
In-Reply-To: <xmqqjz94r8p0.fsf@gitster.g>
On March 4, 2025 12:46 PM, Junio C Hamano wrote:
>A release candidate Git v2.49.0-rc1 is now available for testing at the usual places.
>It is comprised of 367 non-merge commits since v2.48.0, contributed by 68 people,
>17 of which are new faces [*].
Rc1 looks good with OpenSSL 3.4 on NonStop.
Thanks,
Randall
prev parent reply other threads:[~2025-03-05 1:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-04 17:45 [ANNOUNCE] Git v2.49.0-rc1 Junio C Hamano
2025-03-04 18:37 ` Todd Zullinger
2025-03-04 19:42 ` Junio C Hamano
2025-03-05 1:05 ` 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='001e01db8d6a$b4480470$1cd80d50$@nexbridge.com' \
--to=rsbecker@nexbridge.com \
--cc=git-packagers@googlegroups.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=linux-kernel@vger.kernel.org \
/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).