From: Rich Felker <dalias@aerifal.cx>
To: musl@lists.openwall.com
Subject: Wiki for musl?
Date: Wed, 13 Jun 2012 14:14:26 -0400 [thread overview]
Message-ID: <20120613181426.GA10035@brightrain.aerifal.cx> (raw)
Hi all,
Jeremy's offered to help set up us (*) a wiki for musl, which could be
used for recording all of the disorganized and as-yet-unrecorded
community knowledge about package compatibility, patches needed,
common issues, troubleshooting, etc.
My experience using wikis is fairly limited and I have no no idea
which wiki software is best, so I figured I'd best ask the community
who'll (hopefully) be using if you have preferences. While I know lots
of us lean towards the choice that's the least bloated/ugly behind the
scenes, it would probably also be worth considering which choices are
nicest from a standpoint of making contributing/editing a pleasant
experience. :-)
Rich
next reply other threads:[~2012-06-13 18:14 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-13 18:14 Rich Felker [this message]
2012-06-13 18:23 ` Jeremy Huntwork
2012-06-13 18:24 ` Daniel Cegiełka
2012-06-13 18:39 ` Szabolcs Nagy
2012-06-13 18:48 ` Jeremy Huntwork
2012-06-13 18:49 ` Daniel Cegiełka
2012-06-13 18:52 ` Ivan Kanakarakis
2012-06-13 18:51 ` Kurt H Maier
2012-06-13 19:20 ` Jeremy Huntwork
2012-06-13 19:38 ` Rich Felker
2012-06-13 19:54 ` Rich Felker
2012-06-13 20:02 ` Jeremy Huntwork
2012-06-13 20:00 ` Rich Felker
2012-06-13 20:14 ` Jeremy Huntwork
2012-06-13 23:09 ` Kurt H Maier
2012-06-13 23:23 ` Jeremy Huntwork
2012-06-14 0:21 ` Rich Felker
2012-06-14 3:10 ` Kurt H Maier
2012-06-14 3:46 ` Rich Felker
2012-06-14 7:55 ` Szabolcs Nagy
2012-06-14 10:28 ` Conrad Pankoff
2012-06-14 4:00 ` Conrad Pankoff
2012-06-13 19:46 ` Justin Cormack
2012-06-13 20:23 ` Luca Barbato
2012-06-13 20:38 ` nwmcsween
2012-06-13 21:02 ` Ivan Kanakarakis
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=20120613181426.GA10035@brightrain.aerifal.cx \
--to=dalias@aerifal.cx \
--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).