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.36.0-rc1
Date: Sun, 10 Apr 2022 12:14:16 -0400 [thread overview]
Message-ID: <013e01d84cf6$0a507360$1ef15a20$@nexbridge.com> (raw)
In-Reply-To:
On April 8, 2022 7:38 PM, I wrote:
>On April 8, 2022 7:31 PM, Junio C Hamano wrote:
>>A release candidate Git v2.36.0-rc1 is now available for testing at the
>>usual places. It is comprised of 673 non-merge commits since v2.35.0,
>>contributed by 85 people, 25 of which are new faces [*].
>
>We did not make it to t6200 on the previous cycle. Restarting. Note that I did not
>get an answer on changing the PATH to SSH, which is still outstanding for us.
2.36.0-rc1 (ab1f2765f78e) passed on NonStop ia64. We are waiting on x86 results, but this is encouraging (30 hours remaining).
--Randall
next prev parent reply other threads:[~2022-04-10 16:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-08 23:30 [ANNOUNCE] Git v2.36.0-rc1 Junio C Hamano
2022-04-08 23:38 ` rsbecker
2022-04-10 16:14 ` rsbecker [this message]
2022-04-11 11:38 ` rsbecker
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='013e01d84cf6$0a507360$1ef15a20$@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;
as well as URLs for NNTP newsgroup(s).