This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: glibc 2.19 status?
- From: Alexandre Oliva <aoliva at redhat dot com>
- To: Allan McRae <allan at archlinux dot org>
- Cc: "Joseph S. Myers" <joseph at codesourcery dot com>, "Carlos O'Donell" <carlos at redhat dot com>, Roland McGrath <roland at hack dot frob dot com>, libc-alpha <libc-alpha at sourceware dot org>
- Date: Sat, 01 Feb 2014 06:47:47 -0200
- Subject: Re: glibc 2.19 status?
- Authentication-results: sourceware.org; auth=none
- References: <52E649BF dot 5020400 at archlinux dot org> <20140128205657 dot 16DBA74438 at topped-with-meat dot com> <52E9DEB7 dot 4000709 at redhat dot com> <52E9E84F dot 50907 at redhat dot com> <52EA682D dot 90900 at archlinux dot org> <ormwid428y dot fsf at livre dot home> <Pine dot LNX dot 4 dot 64 dot 1401302131080 dot 12540 at digraph dot polyomino dot org dot uk> <orlhxvn1jp dot fsf at livre dot home>
On Jan 31, 2014, Alexandre Oliva <aoliva@redhat.com> wrote:
> Carlos told me he'd have the review completed today/tonight, so it
> wouuld be appreciated if the release could be held up so as to include
> the entire patchset.
He completed the review, and all but one of the patches are in. The
only one that didn't go in was users.texi, for which I posted a revised
patch. There's also an incremental patch that completes threads.texi,
and the patch I just posted for macros.texi.
I'll be offline for a good chunk of today; I shall be back online some
16 hours from now. Should you need to push the release out while I'm
away, please take the patches from the list or from the branch
lxoliva/thread-safety-docs. Note that the branch doesn't touch
ChangeLog, the ChangeLog entries are in the commit messages.
Just don't take the last commit in the branch, unless you feel really
adventurous ;-) It makes @safety sanity checking failures fatal, which
I decided not to do on the grounds that the test script might have some
portability problem lurking in it, and it would suck to have it break
builds with so little time for advance testing.
When I'm back, I'll check for reviews and install/adjust whatever's
approved, then report back wtih the status of the MTASC safety docs.
Thanks,
--
Alexandre Oliva, freedom fighter http://FSFLA.org/~lxoliva/
You must be the change you wish to see in the world. -- Gandhi
Be Free! -- http://FSFLA.org/ FSF Latin America board member
Free Software Evangelist Red Hat Brazil Toolchain Engineer