From: Carlos O'Donell via Libc-alpha <libc-alpha@sourceware.org>
To: libc-alpha <libc-alpha@sourceware.org>
Subject: Development branch is frozen for glibc 2.34 release.
Date: Sat, 31 Jul 2021 22:55:36 -0400 [thread overview]
Message-ID: <301e3e7a-65c1-94b8-e76a-92a3b592034b@redhat.com> (raw)
Community,
I am preparing to cut the branches and test the final glibc 2.34.
Please do not commit anything without asking.
I am not including C.UTF-8 in glibc 2.34, there are too many difficult
changes, but with v7 we're going to be very close, followed by the
nrules == 0 fixes.
We will release still without the pthread conv var fix (Bug 25847),
but I'm going to continue working on that to get a fix in hopefully
next week and backport to the release branch.
--
Cheers,
Carlos.
next reply other threads:[~2021-08-01 2:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-01 2:55 Carlos O'Donell via Libc-alpha [this message]
2021-08-01 15:30 ` Development branch is frozen for glibc 2.34 release Florian Weimer via Libc-alpha
2021-08-01 20:45 ` Carlos O'Donell via Libc-alpha
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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=301e3e7a-65c1-94b8-e76a-92a3b592034b@redhat.com \
--to=libc-alpha@sourceware.org \
--cc=carlos@redhat.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 read-only IMAP folder(s) and NNTP newsgroup(s).