This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: 2.26 release blockers?
- From: Siddhesh Poyarekar <siddhesh at gotplt dot org>
- To: Carlos O'Donell <carlos at redhat dot com>, GNU C Library <libc-alpha at sourceware dot org>
- Date: Sat, 1 Jul 2017 19:43:58 +0530
- Subject: Re: 2.26 release blockers?
- Authentication-results: sourceware.org; auth=none
- References: <6ce02dfc-d8e8-bcd8-4ced-a09293cf1732@redhat.com>
On Saturday 01 July 2017 02:14 AM, Carlos O'Donell wrote:
> I added 2 release blockers:
> https://sourceware.org/glibc/wiki/Release/2.26#Release_blockers.3F
>
> The /etc/resolv.conf reloading and tcache are two important pieces of
> work that I'd like to see go out this release.
>
> What about everyone else?
>
> I assume the people that chimed in on the freeze thread need to decide
> if their work is blocker or desirable?
That's the two I would like to see go in. I believe we have consensus
on Szabolcs' patch for stdio optimization, so that's the other pending
one I'd like to see in 2.26.
I haven't looked at Adhemerval's sysdep-cancel and C11 patches well
enough to comment but based on his comment on the other thread it seems
like the architecture-specific impact should be limited.
I would have liked to see the falkor memcpy go into 2.26, but my fault
for not posting it in time. Early 2.27 it will have to be, and then
maybe have it backported.
Siddhesh