From: Patrick Shirkey <pshirkey@boosthardware.com>
To: Martin Langer <martin-langer@gmx.de>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: Re: doc-page
Date: Mon, 08 Dec 2003 00:43:21 +0900 [thread overview]
Message-ID: <3FD34A99.9050309@boosthardware.com> (raw)
In-Reply-To: 20031205171604.GA19309@tuba.home
Martin Langer wrote:
> Thank you very much, Patrick for the work you've done until now.
>
> But one point I still miss is some kind of browseable Changelog. And a good
> complete changelog history is also good for detecting bugs.
>
> Well, only the users in the mailling lists can know if driver xy has changed
> (or maybe improved) since the last version or not. So normal users have to
> try out each version. And that's far away from perfect IMHO.
>
Nice idea. I think I know how this can be accomplished too.
I'll look into it.
--
Patrick Shirkey - Boost Hardware Ltd.
Http://www.boosthardware.com
Http://www.djcj.org - The Linux Audio Users guide
========================================
Apparently upon the beginning of the barrage, the donkey broke
discipline and panicked, toppling the cart. At that point, the rockets
disconnected from the timer, leaving them strewn around the street.
Tethered to the now toppled cart, the donkey was unable to escape before
the arrival of U.S. troops.
United Press International
Rockets on donkeys hit major Baghdad sites
By P. MITCHELL PROTHERO
Published 11/21/2003 11:13 AM
-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive? Does it
help you create better code? SHARE THE LOVE, and help us help
YOU! Click Here: http://sourceforge.net/donate/
prev parent reply other threads:[~2003-12-07 15:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-04 18:42 doc-page Florian Schmidt
2003-12-04 19:15 ` doc-page Patrick Shirkey
2003-12-05 17:16 ` doc-page Martin Langer
2003-12-07 15:43 ` Patrick Shirkey [this message]
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=3FD34A99.9050309@boosthardware.com \
--to=pshirkey@boosthardware.com \
--cc=alsa-devel@lists.sourceforge.net \
--cc=martin-langer@gmx.de \
/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.