From: Carlos O'Donell <carlos@redhat.com>
To: libc-alpha <libc-alpha@sourceware.org>
Subject: glibc 2.34 release page is up, please add blockers.
Date: Mon, 21 Jun 2021 16:57:13 -0400 [thread overview]
Message-ID: <fcccaa2e-8159-1b77-8cf9-d8c965a515f1@redhat.com> (raw)
The glibc 2.34 release page is up.
https://sourceware.org/glibc/wiki/Release/2.34
I know some of you have been suggesting blockers and desirable
for the release.
Please start listing them so we get them into focus for review
or fixing during the ABI freeze.
--
Cheers,
Carlos.
reply other threads:[~2021-06-21 20:57 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=fcccaa2e-8159-1b77-8cf9-d8c965a515f1@redhat.com \
--to=carlos@redhat.com \
--cc=libc-alpha@sourceware.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).