This is the mail archive of the
mailing list for the glibc project.
Re: GNU C Library release 2.21 scheduled for January 30th 2015.
- From: "H.J. Lu" <hjl dot tools at gmail dot com>
- To: "Carlos O'Donell" <carlos at redhat dot com>
- Cc: GNU C Library <libc-alpha at sourceware dot org>, Marcus Shawcroft <marcus dot shawcroft at linaro dot org>, "Joseph S. Myers" <joseph at codesourcery dot com>, Richard Henderson <rth at redhat dot com>, Mike Frysinger <vapier at gentoo dot org>, Andreas Schwab <schwab at suse dot de>, Chris Metcalf <cmetcalf at tilera dot com>, David Holsgrove <david dot holsgrove at xilinx dot com>, Adhemerval Zanella <azanella at linux dot vnet dot ibm dot com>, Andreas Krebbel <krebbel at linux dot vnet dot ibm dot com>, Kaz Kojima <kkojima at rr dot iij4u dot or dot jp>, David Miller <davem at davemloft dot net>
- Date: Wed, 17 Dec 2014 08:30:13 -0800
- Subject: Re: GNU C Library release 2.21 scheduled for January 30th 2015.
- Authentication-results: sourceware.org; auth=none
- References: <54919EB5 dot 5030209 at redhat dot com>
On Wed, Dec 17, 2014 at 7:18 AM, Carlos O'Donell <firstname.lastname@example.org> wrote:
> I'm volunteering to be the release manager for glibc 2.21.
> The release is planned to go out January 30th 2015.
> I would like to see a freeze no later than January 9th.
> This gives us 3 weeks of testing.
> The testing can be as short as 1 day if all the arches
> come back quickly and without problems.
> Time to polish your patches and get them into 2.21.
I'd like to have a decision on
If we want to support protected data in a DSO with copy relocation,
which will incur run-time and memory overhead, I can prepare ld.so
as well as linker patches. Otherwise, I will make a linker patch
to disallow protected data in a DSO with copy relocation.