From: Eliot Blennerhassett <linux@audioscience.com>
To: ALSA Developers <alsa-devel@alsa-project.org>
Cc: alsa-user@lists.sourceforge.net
Subject: Website to Wiki migration
Date: Wed, 08 Aug 2007 13:42:26 +1200 [thread overview]
Message-ID: <200708081342.26827.linux@audioscience.com> (raw)
Greetings,
IMO the basic content of the static website has been migrated to the wiki.
This doesn't include the following:
* http://alsa-project.org/changes/ Changelogs .txt files are referenced,
assume they are auto generated?
* Contents of http://www.alsa-project.org/alsa/ftp/
* Contents of http://www.alsa-project.org/~iwai/ include "Writing an alsa
driver"
* User added comments in the soundcard matrix are referenced. (Is there any
way to find out which modules in the matrix have user comments attached so
that they can be copied across to the wiki?)
Anything missing - tell about it here:
http://bugtrack.alsa-project.org/main/index.php/MigrationPlan
One proposal for prettier front page is here:
http://bugtrack.alsa-project.org/main/index.php/Talk:Main_Page
Go ahead - criticise, praise, make your own...
cheers
Eliot
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
next reply other threads:[~2007-08-08 1:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-08 1:42 Eliot Blennerhassett [this message]
2007-08-08 15:34 ` Website to Wiki migration Takashi Iwai
2007-08-08 18:31 ` [alsa-devel] " Frank Barknecht
-- strict thread matches above, loose matches on Subject: below --
2007-08-08 22:54 Ash Willis
2007-08-09 0:58 ` Eliot Blennerhassett
2007-08-09 1:28 ` stan
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=200708081342.26827.linux@audioscience.com \
--to=linux@audioscience.com \
--cc=alsa-devel@alsa-project.org \
--cc=alsa-user@lists.sourceforge.net \
/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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.