From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/2371 Path: news.gmane.org!not-for-mail From: Szabolcs Nagy Newsgroups: gmane.linux.lib.musl.general Subject: Re: Summary of 1.0 marketing plan/scheme/nefarious plot from IRC. Date: Fri, 30 Nov 2012 12:08:39 +0100 Message-ID: <20121130110839.GR10895@port70.net> References: <1354222203.2190.17@driftwood> <1354267270.2190.22@driftwood> Reply-To: musl@lists.openwall.com NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1354273734 12267 80.91.229.3 (30 Nov 2012 11:08:54 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 30 Nov 2012 11:08:54 +0000 (UTC) To: musl@lists.openwall.com Original-X-From: musl-return-2375-gllmg-musl=m.gmane.org@lists.openwall.com Fri Nov 30 12:09:07 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 1TeOSw-00085t-DA for gllmg-musl@plane.gmane.org; Fri, 30 Nov 2012 12:09:06 +0100 Original-Received: (qmail 15577 invoked by uid 550); 30 Nov 2012 11:08:51 -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 15569 invoked from network); 30 Nov 2012 11:08:51 -0000 Content-Disposition: inline In-Reply-To: <1354267270.2190.22@driftwood> User-Agent: Mutt/1.5.21 (2010-09-15) Xref: news.gmane.org gmane.linux.lib.musl.general:2371 * Rob Landley [2012-11-30 03:21:10 -0600]: > On 11/29/2012 03:15:38 PM, Justin Cormack wrote: > >Also conferences. FOSDEM is in Feb and is a good place talks still > >open. > > "Lessons learned from writing a new linux/android C library from > scratch" would be a fun talk. Video could be linked from the musl > website... > reminds me that i wanted to collect "software bugs found by musl" (so far there are about 10 formal bugs against the posix standard some of them are serious, there is even an accepted editorial issue in the c11 standard, dalias made several reports against glibc some of them recorded on ewontfix and there are gcc, clang and many pcc issues found by musl +the many patches against software packages some of which already got upstream and various bugs fixed in internal musl code that might affect others: tre, math, crypto..) the design or quality issues are more interesting ones but harder to enumerate (it would be nice to have a collection of broken/dangerous apis and general libc issues that affect others not just musl users, this probably can be part of the documentation effort)