From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/1016 Path: news.gmane.org!not-for-mail From: John Spencer Newsgroups: gmane.linux.lib.musl.general Subject: Re: printf POSIX compliance Date: Fri, 08 Jun 2012 18:38:31 +0200 Message-ID: <4FD22A87.1030709@barfooze.de> References: <20120608144423.GN163@brightrain.aerifal.cx> <20120608145519.GP163@brightrain.aerifal.cx> <20120608150618.GB17860@port70.net> <20120608152935.GQ163@brightrain.aerifal.cx> <20120608155322.GR163@brightrain.aerifal.cx> Reply-To: musl@lists.openwall.com NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Trace: dough.gmane.org 1339172985 31569 80.91.229.3 (8 Jun 2012 16:29:45 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Fri, 8 Jun 2012 16:29:45 +0000 (UTC) Cc: rrt@sc3d.org To: musl@lists.openwall.com Original-X-From: musl-return-1017-gllmg-musl=m.gmane.org@lists.openwall.com Fri Jun 08 18:29:44 2012 Return-path: Envelope-to: gllmg-musl@plane.gmane.org Original-Received: from mother.openwall.net ([195.42.179.200]) by plane.gmane.org with smtp (Exim 4.69) (envelope-from ) id 1Sd24G-0002eQ-4h for gllmg-musl@plane.gmane.org; Fri, 08 Jun 2012 18:29:44 +0200 Original-Received: (qmail 4063 invoked by uid 550); 8 Jun 2012 16:29:44 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Original-Received: (qmail 4055 invoked from network); 8 Jun 2012 16:29:44 -0000 User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.14) Gecko/20110221 SUSE/3.1.8 Mail/1.0 In-Reply-To: Xref: news.gmane.org gmane.linux.lib.musl.general:1016 Archived-At: On 06/08/2012 06:16 PM, Reuben Thomas wrote: > > The maintainers (Gary Vaughan and Eric Blake) are both active, so I > think it's worth it; Eric works on gnulib too. > > You're right that of course for practical purposes it requires new > releases using the fixed version of gnulib, but many of these issues > (this one included) affect multiple packages, and also it's possible > to "repair" a broken package by refreshing gnulib before building. > i was recently following a conversation in #gdb where GNU people (!) were trying to update gnulib and failed... it took them about 5 hours to get everything fixed. i don't think most users of gnulib want to go through this mess...