From: Junio C Hamano <gitster@pobox.com>
To: <rsbecker@nexbridge.com>
Cc: <git@vger.kernel.org>
Subject: Re: [ANNOUNCE] Git v2.48.0-rc1
Date: Wed, 01 Jan 2025 08:54:08 -0800 [thread overview]
Message-ID: <xmqqwmfewk3z.fsf@gitster.g> (raw)
In-Reply-To: <043301db5ba8$323355a0$969a00e0$@nexbridge.com> (rsbecker@nexbridge.com's message of "Tue, 31 Dec 2024 12:19:43 -0500")
<rsbecker@nexbridge.com> writes:
> On December 30, 2024 12:33 PM, Junio C Hamano wrote:
>>A release candidate Git v2.48.0-rc1 is now available for testing at the usual places.
>>It is comprised of 549 non-merge commits since v2.47.0, contributed by 81 people,
>>33 of which are new faces [*].
>
> FYI: NonStop builds/tests look good for this release candidate. Thank you for all your
> efforts.
Thanks.
prev parent reply other threads:[~2025-01-01 16:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-30 17:33 [ANNOUNCE] Git v2.48.0-rc1 Junio C Hamano
2024-12-31 17:19 ` rsbecker
2025-01-01 16:54 ` Junio C Hamano [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=xmqqwmfewk3z.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=rsbecker@nexbridge.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).