This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: The 2.20 release code freeze is very near
- From: OndÅej BÃlka <neleai at seznam dot cz>
- To: Carlos O'Donell <carlos at redhat dot com>
- Cc: Allan McRae <allan at archlinux dot org>, libc-alpha <libc-alpha at sourceware dot org>
- Date: Thu, 10 Jul 2014 15:19:12 +0200
- Subject: Re: The 2.20 release code freeze is very near
- Authentication-results: sourceware.org; auth=none
- References: <53B3D952 dot 6090906 at archlinux dot org> <53B49B62 dot 2070704 at redhat dot com>
On Wed, Jul 02, 2014 at 07:53:06PM -0400, Carlos O'Donell wrote:
> On 07/02/2014 06:05 AM, Allan McRae wrote:
> > Anything else that needs tracked should be added to the release wiki
> > page. E.g. this was mentioned on the mailing list as targeted for 2.20:
>
> I would like to reiterate what I already added to the page, that the
> Linux kernel now has file descriptor based locking and it's in the
> stable kernel. Therefore we should be exposing those flags and adding
> their documentation to our manual.
>
> Michael Kerrisk and I have reviewed this a couple of times over, and
> I need to do a final pass and commit for Jeff Layton. Nobody has objected
> to this, and it seems like a good feature.
>
> One might argue that the sneaky way to get new APIs into glibc is to
> force them through the kernel side via existing syscalls and new flags ;-)
>
Yes, I was waiting when you will commit it for a while.