Date: Sun, 1 Jan 2017 21:33:17 -0500 From: Rich Felker <dalias@...c.org> To: musl@...ts.openwall.com Subject: Re: musl new-year's infrastructure resolutions 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
Powered by blists - more mailing lists
Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.