From: Vineet Gupta <Vineet.Gupta1@synopsys.com>
To: Carlos O'Donell <carlos@redhat.com>,
libc-alpha <libc-alpha@sourceware.org>,
Joseph Myers <joseph@codesourcery.com>,
Andreas Schwab <schwab@suse.de>,
"Ryan S. Arnold" <ryan.arnold@gmail.com>,
Mark Brown <ms_brown@sbcglobal.net>,
Paul Eggert <eggert@cs.ucla.edu>,
Jakub Jelinek <jakub@redhat.com>,
Maxim Kuvyrkov <maxim.kuvyrkov@linaro.org>,
"Dmitry V. Levin" <ldv@altlinux.org>,
Aurelien Jarno <aurelien@aurel32.net>,
Romain Naour <romain.naour@smile.fr>,
Stan Shebs <stanshebs@google.com>, Khem Raj <raj.khem@gmail.com>,
Florian Weimer <fweimer@redhat.com>
Cc: arcml <linux-snps-arc@lists.infradead.org>
Subject: Re: glibc 2.32 --- Two weeks to ABI freeze. Volunteers for release manager?
Date: Sat, 20 Jun 2020 05:07:00 +0000 [thread overview]
Message-ID: <e00be318-568b-2da8-20a9-c504ac545505@synopsys.com> (raw)
In-Reply-To: <a5b614eb-2344-2944-96f6-3560fae2a3da@redhat.com>
On 6/16/20 5:02 PM, Carlos O'Donell via Libc-alpha wrote:
> The GNU C Library 2.32 release is scheduled for August 1st 2020.
>
> The ABI freeze should happen between July 1st 2020.
>
> We have 2 more weeks before ABI freeze.
ARC port seems pretty close to production quality, with multiple rounds of reviews
and updates already so it would be good to wrap it up too. All the accompanying
generic changes have already been merged.
Thx,
-Vineet
_______________________________________________
linux-snps-arc mailing list
linux-snps-arc@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-snps-arc
parent reply other threads:[~2020-06-20 5:07 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <a5b614eb-2344-2944-96f6-3560fae2a3da@redhat.com>]
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=e00be318-568b-2da8-20a9-c504ac545505@synopsys.com \
--to=vineet.gupta1@synopsys.com \
--cc=aurelien@aurel32.net \
--cc=carlos@redhat.com \
--cc=eggert@cs.ucla.edu \
--cc=fweimer@redhat.com \
--cc=jakub@redhat.com \
--cc=joseph@codesourcery.com \
--cc=ldv@altlinux.org \
--cc=libc-alpha@sourceware.org \
--cc=linux-snps-arc@lists.infradead.org \
--cc=maxim.kuvyrkov@linaro.org \
--cc=ms_brown@sbcglobal.net \
--cc=raj.khem@gmail.com \
--cc=romain.naour@smile.fr \
--cc=ryan.arnold@gmail.com \
--cc=schwab@suse.de \
--cc=stanshebs@google.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 NNTP newsgroup(s).