From: "Randall S. Becker" <rsbecker@nexbridge.com>
To: "'Junio C Hamano'" <gitster@pobox.com>, <git@vger.kernel.org>
Cc: <git-packagers@googlegroups.com>
Subject: RE: [ANNOUNCE] Git v2.26.0-rc2
Date: Thu, 19 Mar 2020 09:52:25 -0400 [thread overview]
Message-ID: <01a001d5fdf5$a2b1e500$e815af00$@nexbridge.com> (raw)
In-Reply-To: <xmqqa74fj30p.fsf@gitster.c.googlers.com>
On March 16, 2020 7:26 PM, Junio C Hamano:
> A release candidate Git v2.26.0-rc2 is now available for testing at the usual
> places. It is comprised of 463 non-merge commits since v2.25.0, contributed
> by 48 people, 10 of which are new faces.
Test results from the NonStop build:
Everything looks good. t9001 and t9020 fail as usual because they should really not be run on the platform.
Thanks for all of your hard work.
Regards,
Randall
prev parent reply other threads:[~2020-03-19 13:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-16 23:25 [ANNOUNCE] Git v2.26.0-rc2 Junio C Hamano
2020-03-19 13:52 ` Randall S. Becker [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='01a001d5fdf5$a2b1e500$e815af00$@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).