This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: glibc 2.23 --- Hard freeze starting
- From: Steven Munroe <munroesj at linux dot vnet dot ibm dot com>
- To: Siddhesh Poyarekar <sid at reserved-bit dot com>
- Cc: Adhemerval Zanella <adhemerval dot zanella at linaro dot org>, Roland McGrath <roland at hack dot frob dot com>, GNU C Library <libc-alpha at sourceware dot org>
- Date: Thu, 21 Jan 2016 13:06:13 -0600
- Subject: Re: glibc 2.23 --- Hard freeze starting
- Authentication-results: sourceware.org; auth=none
- References: <569D4A42 dot 7030006 at linaro dot org> <20160120225625 dot 5CE8E2C3B00 at topped-with-meat dot com> <56A0E3C3 dot 5010704 at linaro dot org> <1453391129 dot 19764 dot 4 dot camel at oc7878010663> <20160121155626 dot GQ3334 at devel dot intra dot reserved-bit dot com> <1453396427 dot 19764 dot 13 dot camel at oc7878010663> <20160121172013 dot GR3334 at devel dot intra dot reserved-bit dot com>
- Reply-to: munroesj at linux dot vnet dot ibm dot com
On Thu, 2016-01-21 at 22:50 +0530, Siddhesh Poyarekar wrote:
> On Thu, Jan 21, 2016 at 11:13:47AM -0600, Steven Munroe wrote:
> > The full context is that the above is not acceptable to the distros.
> > They insist on an common and dynamic mechanism to enable/disable.
>
> Distros can backport the tunables patchset to any release since it
> does not change the ABI.
But not until it is accepted upstream in GLIBC. There are deadlines
associated with other communities that where missed and are being
missed.
>
> > I fear that this group will not find consensus in the absence of some
> > forcing issue. Otherwise the discussion (with lack of consensus) and
> > associate delays will go on indefinitely.
> >
> > This has been delayed too long. It is time to end the debate.
>
> The delay was entirely my fault. I was unable to get back on this
> task in time to allow enough time for everyone to review and come to a
> consensus.
>
If you could not address this in a timely then it would have been best
if you stated so earlier and handed this effort off to other interested
parties.
And we (powerpc team and I) should have been clearer on our requirements
and timelines.