This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: 2.25 Freeze getting slushy soon
- From: Joseph Myers <joseph at codesourcery dot com>
- To: Siddhesh Poyarekar <siddhesh at gotplt dot org>
- Cc: "Gabriel F. T. Gomes" <gftg at linux dot vnet dot ibm dot com>, "libc-alpha at sourceware dot org" <libc-alpha at sourceware dot org>, Adhemerval Zanella <adhemerval dot zanella at linaro dot org>
- Date: Mon, 2 Jan 2017 18:52:51 +0000
- Subject: Re: 2.25 Freeze getting slushy soon
- Authentication-results: sourceware.org; auth=none
- References: <e33a0a85-e338-4dd4-a7bd-f75f7eb00c23@gotplt.org> <20170102110558.1528d9d6@keller> <alpine.DEB.2.20.1701021351380.28945@digraph.polyomino.org.uk> <11dc5eed-59d7-0884-6b24-8e4ed5181cbb@gotplt.org>
On Tue, 3 Jan 2017, Siddhesh Poyarekar wrote:
> On Monday 02 January 2017 07:24 PM, Joseph Myers wrote:
> > As part of the review, I'll want to do build-many-glibcs.py builds for
> > various configurations for which architecture-specific files are affected
> > (possibly including configurations not currently covered by
> > build-many-glibcs.py). Right now this means the full review is blocked by
> > the sparc build breakage.
>
> Would it be reasonable to ignore sparc results for now and review based
> on the remaining architectures? If this patchset causes failures in
> sparc (that we discover later), it could be fixed in the freeze window.
I'd rather get the build fix in first.
--
Joseph S. Myers
joseph@codesourcery.com