From: <rsbecker@nexbridge.com>
To: "'Junio C Hamano'" <gitster@pobox.com>, <git@vger.kernel.org>
Subject: RE: [ANNOUNCE] Git v2.48.0-rc2
Date: Mon, 6 Jan 2025 15:47:45 -0500 [thread overview]
Message-ID: <000501db607c$40c009a0$c2401ce0$@nexbridge.com> (raw)
In-Reply-To: <xmqqbjwjyalr.fsf@gitster.g>
On January 6, 2025 3:02 PM, Junio C Hamano wrote:
>A release candidate Git v2.48.0-rc2 is now available for testing at the usual places.
>It is comprised of 584 non-merge commits since v2.47.0, contributed by 81 people,
>33 of which are new faces... <snip>
Our main build/test machine is undergoing to periodic maintenance and upgrading so
we are on an older box. The build/test cycle on this one is about 40 hours, so apologies
that results will be delayed for NonStop. This one is being done on our ia64 box instead
of x86.
--Randall
prev parent reply other threads:[~2025-01-06 20:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-06 20:02 [ANNOUNCE] Git v2.48.0-rc2 Junio C Hamano
2025-01-06 20:47 ` 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='000501db607c$40c009a0$c2401ce0$@nexbridge.com' \
--to=rsbecker@nexbridge.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;
as well as URLs for NNTP newsgroup(s).