From: Carlos O'Donell via Libc-alpha <libc-alpha@sourceware.org>
To: libc-alpha <libc-alpha@sourceware.org>
Subject: Development open for glibc 2.33
Date: Tue, 4 Aug 2020 23:46:14 -0400 [thread overview]
Message-ID: <7e306089-2c11-559d-4d0c-fe8c566b6460@redhat.com> (raw)
The release branch for glibc 2.32 has been created.
The development branch is open for glibc 2.33.
Please feel free to start development again!
Happy hacking :-)
--
Cheers,
Carlos.
next reply other threads:[~2020-08-05 3:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-05 3:46 Carlos O'Donell via Libc-alpha [this message]
2020-08-05 7:06 ` Merged Gnulib changes into glibc Paul Eggert
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=7e306089-2c11-559d-4d0c-fe8c566b6460@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).