This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: glibc 2.22 --- Master is frozen.
- From: "Carlos O'Donell" <carlos at redhat dot com>
- To: "H.J. Lu" <hjl dot tools at gmail dot com>
- Cc: Siddhesh Poyarekar <siddhesh at redhat dot com>, GNU C Library <libc-alpha at sourceware dot org>, Carlos Eduardo Seo <cseo at linux dot vnet dot ibm dot com>
- Date: Mon, 20 Jul 2015 11:41:20 -0400
- Subject: Re: glibc 2.22 --- Master is frozen.
- Authentication-results: sourceware.org; auth=none
- References: <55A3EDC2 dot 1060604 at redhat dot com> <55A3EDEA dot 3040502 at redhat dot com> <20150715112142 dot GK29227 at spoyarek dot pnq dot redhat dot com> <55A6677F dot 5010106 at redhat dot com> <CAMe9rOqixjmheayDby9JePZ2Pi-J_3mNB6M85kKqFG76nsBGOA at mail dot gmail dot com>
On 07/20/2015 11:40 AM, H.J. Lu wrote:
> On Wed, Jul 15, 2015 at 7:00 AM, Carlos O'Donell <carlos@redhat.com> wrote:
>> On 07/15/2015 07:21 AM, Siddhesh Poyarekar wrote:
>>> On Mon, Jul 13, 2015 at 12:57:14PM -0400, Carlos O'Donell wrote:
>>>> On 07/13/2015 12:56 PM, Carlos O'Donell wrote:
>>>>> Master is now frozen. Please don't commit unless you get an ACK
>>>>> from me. Please respond to this thread if you have any patches
>>>>> pending review for the release.
>>>
>>> We discussed this offline, but to state publicly, I'd like to set the
>>> TLS deadlock fixes as blockers for 2.22.
>>
>> Agreed.
>>
>> Already added to the release page:
>> https://sourceware.org/glibc/wiki/Release/2.22
>
> I'd like to add
>
> https://sourceware.org/bugzilla/show_bug.cgi?id=18696
>
> to 2.22 blocker.
What are the implications of the breakage and the fix on machine testing?
c.