From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/10844 Path: news.gmane.org!.POSTED!not-for-mail From: Rich Felker Newsgroups: gmane.linux.lib.musl.general Subject: Re: musl new-year's infrastructure resolutions Date: Sun, 1 Jan 2017 21:33:17 -0500 Message-ID: <20170102023317.GY1555@brightrain.aerifal.cx> References: <20161231233747.GV1555@brightrain.aerifal.cx> <58698490.4040904@adelielinux.org> <20170102023139.GX1555@brightrain.aerifal.cx> Reply-To: musl@lists.openwall.com NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: blaine.gmane.org 1483324422 17851 195.159.176.226 (2 Jan 2017 02:33:42 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Mon, 2 Jan 2017 02:33:42 +0000 (UTC) User-Agent: Mutt/1.5.21 (2010-09-15) To: musl@lists.openwall.com Original-X-From: musl-return-10857-gllmg-musl=m.gmane.org@lists.openwall.com Mon Jan 02 03:33:38 2017 Return-path: Envelope-to: gllmg-musl@m.gmane.org Original-Received: from mother.openwall.net ([195.42.179.200]) by blaine.gmane.org with smtp (Exim 4.84_2) (envelope-from ) id 1cNsRE-00030n-1p for gllmg-musl@m.gmane.org; Mon, 02 Jan 2017 03:33:28 +0100 Original-Received: (qmail 3337 invoked by uid 550); 2 Jan 2017 02:33:30 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-ID: Original-Received: (qmail 3319 invoked from network); 2 Jan 2017 02:33:29 -0000 Content-Disposition: inline In-Reply-To: <20170102023139.GX1555@brightrain.aerifal.cx> Original-Sender: Rich Felker Xref: news.gmane.org gmane.linux.lib.musl.general:10844 Archived-At: On Sun, Jan 01, 2017 at 09:31:39PM -0500, Rich Felker wrote: > > > Documentation. Existing manual should probably become a public git > > > repo that contributors can submit patches/PRs for. Putting > > > together lists of (1) what's outdated in the current one, and (2) > > > what new content would be most valuable, might be a good place to > > > start and one that could benefit from community involvement. > > > > I would love to contribute good/better documentation to musl. If you > > could make those lists I would definitely see what I could contribute. > > IMO the most important things that need to be documented are: > > 1. Everything implementation-defined that ISO C or POSIX requires. > Just making the list of these things is a big task. I think I > started it once and have notes but I don't remember for sure. > > 2. A list of all the nonstandard extensions supported by musl, both > extension functionality to standard functions as well as extension > functions, with documentation on how they behave. This would > probably take the form of a reference to some other document (like > Linux man pages) or implementation (like glibc) with differences > explained clearly. BTW for reference here is the current (well, outdated) manual: http://www.musl-libc.org/doc/1.0.0/manual.html http://www.musl-libc.org/doc/1.0.0/manual.txt http://www.musl-libc.org/doc/1.0.0/manual.md The md version is the source for the others. Rich