[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.21.1811151628490.27351@digraph.polyomino.org.uk>
Date: Thu, 15 Nov 2018 16:29:43 +0000
From: Joseph Myers <joseph@...esourcery.com>
To: "Theodore Y. Ts'o" <tytso@....edu>
CC: Daniel Colascione <dancol@...gle.com>,
Szabolcs Nagy <Szabolcs.Nagy@....com>,
Dave P Martin <Dave.Martin@....com>, nd <nd@....com>,
Florian Weimer <fweimer@...hat.com>,
"Michael Kerrisk (man-pages)" <mtk.manpages@...il.com>,
linux-kernel <linux-kernel@...r.kernel.org>,
Joel Fernandes <joelaf@...gle.com>,
Linux API <linux-api@...r.kernel.org>,
Willy Tarreau <w@....eu>, Vlastimil Babka <vbabka@...e.cz>,
Carlos O'Donell <carlos@...hat.com>,
"libc-alpha@...rceware.org" <libc-alpha@...rceware.org>
Subject: Re: Official Linux system wrapper library?
On Thu, 15 Nov 2018, Theodore Y. Ts'o wrote:
> That's great. But is it or is it not true (either de jure or de
> facto) that "a single active glibc developer" can block a system call
> from being supported by glibc by objecting? And if not, under what is
> the process by resolving a conflict?
We use a consensus-building process as described at
<https://sourceware.org/glibc/wiki/Consensus>.
--
Joseph S. Myers
joseph@...esourcery.com
Powered by blists - more mailing lists