From: Carlos O'Donell <carlos@redhat.com>
To: libc-alpha <libc-alpha@sourceware.org>,
Szabolcs Nagy <szabolcs.nagy@arm.com>,
Vineet Gupta <Vineet.Gupta1@synopsys.com>,
Joseph Myers <joseph@codesourcery.com>,
Phil Blundell <pb@pbcl.net>,
Marcus Shawcroft <Marcus.Shawcroft@arm.com>,
Mao Han <han_mao@c-sky.com>,
John David Anglin <dave.anglin@bell.net>,
Mike Frysinger <vapier@gentoo.org>,
Andreas Schwab <schwab@suse.de>,
Chung-Lin Tang <cltang@codesourcery.com>,
Stafford Horne <shorne@gmail.com>,
Tulio Magno Quites Machado Filho <tuliom@linux.ibm.com>,
DJ Delorie <dj@redhat.com>
Subject: glibc 2.35 - Machine testing.
Date: Fri, 28 Jan 2022 14:13:03 -0500 [thread overview]
Message-ID: <cd3ae5b2-13f3-e39f-7ac8-0271805234c6@redhat.com> (raw)
Machine maintainers,
Please start testing your targets for glibc 2.35.
Please report results to the wiki here:
https://sourceware.org/glibc/wiki/Release/2.35#Build_and_test_results
--
Cheers,
Carlos.
reply other threads:[~2022-01-28 19:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=cd3ae5b2-13f3-e39f-7ac8-0271805234c6@redhat.com \
--to=carlos@redhat.com \
--cc=Marcus.Shawcroft@arm.com \
--cc=Vineet.Gupta1@synopsys.com \
--cc=cltang@codesourcery.com \
--cc=dave.anglin@bell.net \
--cc=dj@redhat.com \
--cc=han_mao@c-sky.com \
--cc=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.org \
--cc=pb@pbcl.net \
--cc=schwab@suse.de \
--cc=shorne@gmail.com \
--cc=szabolcs.nagy@arm.com \
--cc=tuliom@linux.ibm.com \
--cc=vapier@gentoo.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 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 read-only IMAP folder(s) and NNTP newsgroup(s).