This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: Code freeze for glibc-2.19
- From: "Carlos O'Donell" <carlos at redhat dot com>
- To: Allan McRae <allan at archlinux dot org>, libc-alpha <libc-alpha at sourceware dot org>
- Cc: Paul Pluzhnikov <ppluzhnikov at google dot com>, Andrew Hunter <ahh at google dot com>
- Date: Wed, 01 Jan 2014 22:57:54 -0500
- Subject: Re: Code freeze for glibc-2.19
- Authentication-results: sourceware.org; auth=none
- References: <52C40F69 dot 9050604 at archlinux dot org> <52C4DD69 dot 9020809 at redhat dot com> <52C4E120 dot 5040100 at archlinux dot org>
On 01/01/2014 10:46 PM, Allan McRae wrote:
>> (4) Async signal-safe TLS access
>> - Reviewed by mew today 2014-01-01 (version 5 of patch)
>> - Has a test case.
>> - Contains P&C comments about barriers.
>>
>> Given my review I think it's ready to checkin for 2.19.
>>
>> However, the final call is Allan's.
>>
>> Allan, I've tried to give you enough background here for you
>> to make a call about this patch. That's what I would have
>> expected from anyone else trying to get a feature into 2.19
>> at or near the deadline :-)
>>
>> Comments?
>
> That explanation is exactly what I needed. It was not apparent from the
> wiki that this patch was part of a set that was mostly checked in and a
> final revision had been made.
>
> The patch is fine to check-in.
Yes, sorry about that, I've updated the wiki to reflect current status.
The line item about this feature was simply a place holder to prevent
you from cutting the release branch before we ironed out the status.
Thanks for your help organizing the release!
Cheers,
Carlos.