This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: glibc 2.19 status?
- From: "Carlos O'Donell" <carlos at redhat dot com>
- To: Alexandre Oliva <aoliva at redhat dot com>, Allan McRae <allan at archlinux dot org>
- Cc: "Joseph S. Myers" <joseph at codesourcery dot com>, Roland McGrath <roland at hack dot frob dot com>, libc-alpha <libc-alpha at sourceware dot org>
- Date: Mon, 03 Feb 2014 15:32:19 -0500
- 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> <or38k3jk24 dot fsf at livre dot home> <orsis1hxg0 dot fsf at livre dot home> <orob2ohu5a dot fsf at livre dot home>
On 02/03/2014 02:29 PM, Alexandre Oliva wrote:
> On Feb 2, 2014, Alexandre Oliva <aoliva@redhat.com> wrote:
>
>> On Feb 1, 2014, Alexandre Oliva <aoliva@redhat.com> wrote:
>>> 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.
>
>> I did, yesterday and today, and I couldn't find any reviews for the 3
>> pending patches, so they're still on hold. I suppose this situation
>> will be addressed tomorrow, if not later today. Apologies for any
>> delays this may have caused.
>
> Ok, all of the MTASC safety patches are in now.
Please add a NEWS entry for this work! :-)
e.g.
* The GNU C Library manual now includes preliminary thread, signal,
and cancellation safety information for all documented functions.
Each documented function now continues a safety note after the
prototype. Functions are documented as being safe or unsafe with
the reason listed by a series of keywords. The project expects
to expand on this information, eventually making guarantees about
safety that match the POSIX and ISO C requirements.
Cheers,
Carlos.