From: <rsbecker@nexbridge.com>
To: <git@vger.kernel.org>
Subject: Re: [ANNOUNCE] Git v2.35.0-rc1
Date: Mon, 17 Jan 2022 11:05:31 -0500 [thread overview]
Message-ID: <026201d80bbc$10a251a0$31e6f4e0$@nexbridge.com> (raw)
In-Reply-To:
On January 14, 2022 9:19 PM, Junio wrote:
> A release candidate Git v2.35.0-rc1 is now available for testing at the usual places.
> It is comprised of 467 non-merge commits since v2.34.0, contributed by 80
> people, 32 of which are new faces [*].
FYI: rc1 built/test (mostly) passes on both NonStop x86 and ia64 platforms.
We seem to have a recurrence of a transient failure in t5562 from a few releases ago. Retesting makes the problem disappear.
Subtest 8
#
# test_env HTTP_CONTENT_ENCODING="gzip" test_http_env upload empty_body &&
# ! verify_http_result "200 OK"
#
Subtest 14
#
# test_env HTTP_CONTENT_ENCODING="gzip" test_http_env receive empty_body &&
# ! verify_http_result "200 OK"
#
Am I mistaken that using the ! verify_http_result construct is not recommended or am I misremembering the discussion?
Regards,
--Randall
next prev parent reply other threads:[~2022-01-17 16:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-15 2:18 [ANNOUNCE] Git v2.35.0-rc1 Junio C Hamano
2022-01-17 16:05 ` rsbecker [this message]
2022-01-17 18:42 ` Junio C Hamano
2022-01-17 18:52 ` 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='026201d80bbc$10a251a0$31e6f4e0$@nexbridge.com' \
--to=rsbecker@nexbridge.com \
--cc=git@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.