From: <rsbecker@nexbridge.com>
To: "'Junio C Hamano'" <gitster@pobox.com>
Cc: "'Git Mailing List'" <git@vger.kernel.org>,
<git-packagers@googlegroups.com>
Subject: RE: [ANNOUNCE] Git v2.36.0-rc0 - Build failure on NonStops
Date: Wed, 6 Apr 2022 18:32:48 -0400 [thread overview]
Message-ID: <048601d84a06$416fe120$c44fa360$@nexbridge.com> (raw)
In-Reply-To: <xmqqsfqqxat4.fsf@gitster.g>
>-----Original Message-----
On April 6, 2022 3:38 PM, Junio C Hamano wrote
><rsbecker@nexbridge.com> writes:
>
>> I have no explanation on why this and the PATH issue showed up at
>> 2.36.0-rc0 and not at 2.35.1. 2.35.0. Our build/test cycles are
>> thorough but only on the releases and rc* ...
>
>Ah, OK, so I had a wrong impression, which explains my puzzlement.
>
>I somehow thought that you caught us soon after stuff got merged to
'master',
>and sometimes even to 'next', for a few times before.
I am working on getting a much faster system. Once that happens, I hope we
can increase the cadence of my test cycle.
Regards,
Randall
next prev parent reply other threads:[~2022-04-06 22:33 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-04 22:30 [ANNOUNCE] Git v2.36.0-rc0 - Build failure on NonStops rsbecker
2022-04-04 22:32 ` Junio C Hamano
2022-04-04 22:40 ` rsbecker
2022-04-05 0:26 ` Carlo Marcelo Arenas Belón
2022-04-05 0:54 ` Carlo Marcelo Arenas Belón
2022-04-05 2:59 ` rsbecker
2022-04-05 4:28 ` Carlo Marcelo Arenas Belón
2022-04-05 8:10 ` brian m. carlson
2022-04-05 22:47 ` Carlo Arenas
2022-04-05 23:09 ` rsbecker
2022-04-06 16:04 ` Junio C Hamano
2022-04-05 12:33 ` rsbecker
2022-04-05 1:56 ` rsbecker
2022-04-06 16:14 ` Junio C Hamano
2022-04-06 16:23 ` rsbecker
2022-04-06 19:37 ` Junio C Hamano
2022-04-06 22:32 ` rsbecker [this message]
2022-04-06 20:01 ` 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='048601d84a06$416fe120$c44fa360$@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).