From: Joseph Myers <joseph@codesourcery.com>
To: Adhemerval Zanella Netto <adhemerval.zanella@linaro.org>
Cc: <libc-alpha@sourceware.org>, Carlos O'Donell <carlos@redhat.com>
Subject: Re: Status and plans for glibc 2.37 release on February 1st 2023
Date: Tue, 3 Jan 2023 18:50:57 +0000 [thread overview]
Message-ID: <cfb3217f-136d-2cb8-2a6e-9168534b2054@codesourcery.com> (raw)
In-Reply-To: <78d28afe-779b-3661-a234-21cfa2f12f2a@linaro.org>
I've put my C2x strtol / scanf changes on the desirable list. (Copyright
date updates for new files to include 2023 should be assumed for these
patches.)
--
Joseph S. Myers
joseph@codesourcery.com
prev parent reply other threads:[~2023-01-03 18:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-31 18:11 Carlos O'Donell
2023-01-03 14:28 ` Siddhesh Poyarekar
2023-01-03 15:23 ` Adhemerval Zanella Netto
2023-01-03 18:50 ` Joseph Myers [this message]
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=cfb3217f-136d-2cb8-2a6e-9168534b2054@codesourcery.com \
--to=joseph@codesourcery.com \
--cc=adhemerval.zanella@linaro.org \
--cc=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).