From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Re: musl new-year's infrastructure resolutions
Date: Sun, 1 Jan 2017 21:33:17 -0500 [thread overview]
Message-ID: <20170102023317.GY1555@brightrain.aerifal.cx> (raw)
In-Reply-To: <20170102023139.GX1555@brightrain.aerifal.cx>
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
next prev parent reply other threads:[~2017-01-02 2:33 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-31 23:37 Rich Felker
2017-01-01 22:37 ` A. Wilcox
2017-01-02 2:31 ` Rich Felker
2017-01-02 2:33 ` Rich Felker [this message]
2017-01-02 5:32 ` A. Wilcox
2017-01-02 5:40 ` Rich Felker
2017-01-02 6:39 ` Khem Raj
2017-01-02 16:58 ` Rich Felker
2017-01-02 18:11 ` Alexander Monakov
2017-01-02 18:23 ` Rich Felker
2017-01-02 18:15 ` Solar Designer
2017-01-02 18:25 ` Rich Felker
2017-01-02 18:27 ` Kurt H Maier
2017-01-02 18:36 ` Rich Felker
2017-01-02 18:52 ` Kurt H Maier
2017-01-02 19:16 ` Rich Felker
2017-01-02 20:06 ` Kurt H Maier
2017-01-02 22:59 ` A. Wilcox
2017-01-02 23:09 ` Kurt H Maier
2017-01-02 19:10 ` Matias A. Fonzo
2017-01-02 19:18 ` Rich Felker
2017-01-02 19:28 ` Matias A. Fonzo
2017-01-03 1:20 ` Laurent Bercot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170102023317.GY1555@brightrain.aerifal.cx \
--to=dalias@libc.org \
--cc=musl@lists.openwall.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).