From: Carlos O'Donell <carlos@redhat.com>
To: libc-alpha <libc-alpha@sourceware.org>
Subject: Open for glibc 2.37 development.
Date: Sun, 31 Jul 2022 07:57:06 -0400 [thread overview]
Message-ID: <9cf7da4a-54c5-7237-f4c2-fd8b0f5f53de@redhat.com> (raw)
Community,
The master branch is open for glibc 2.37 development.
Please commit liberal fixes to release/2.36/master since this will be
actively used by downstream distributions which are tracking the
release branch.
--
Cheers,
Carlos.
next reply other threads:[~2022-07-31 11:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-31 11:57 Carlos O'Donell [this message]
2022-08-01 21:47 ` Michael Hudson-Doyle
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=9cf7da4a-54c5-7237-f4c2-fd8b0f5f53de@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).