From: "Ronald S. Bultje" <rbultje@ronald.bitfreak.net>
To: Jaroslav Kysela <perex@suse.cz>
Cc: Takashi Iwai <tiwai@suse.de>, alsa-devel@lists.sourceforge.net
Subject: Re: why do elements disappear?
Date: Thu, 03 Mar 2005 13:25:22 +0100 [thread overview]
Message-ID: <1109852722.2840.51.camel@tux.lan> (raw)
In-Reply-To: <Pine.LNX.4.58.0503031015090.3041@pnote.perex-int.cz>
Hi,
On Thu, 2005-03-03 at 10:17, Jaroslav Kysela wrote:
> Any patches for alsa-lib providing better documentation are appreciated.
You probably don't want that. The documentation that I would provide
with my current knowledge of ALSA would suck so badly that it'd cause
only more uproar. ;).
Anyway, what I'm trying to say is: thanks for the docs so far, they've
continued to improve all the time since a few years back (when I first
looked at ALSA), and I think that's great. Through this, I'm trying to
provide constructive criticism, not slay you guys down, so that it will
get yet better from here on. You guys are doing good work and I'm happy
with that.
> Look for sevents() function.
Thanks.
Ronald
--
Ronald S. Bultje <rbultje@ronald.bitfreak.net>
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
next prev parent reply other threads:[~2005-03-03 12:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-15 21:12 why do elements disappear? Ronald S. Bultje
2005-02-16 10:42 ` Takashi Iwai
[not found] ` <m2r7jgpvw9.fsf@vador.mandrakesoft.com>
2005-02-16 11:52 ` Takashi Iwai
2005-02-16 12:14 ` Thierry Vignaud
2005-02-16 12:12 ` Takashi Iwai
2005-02-16 12:31 ` Thierry Vignaud
2005-03-03 8:57 ` Ronald S. Bultje
2005-03-03 9:17 ` Jaroslav Kysela
2005-03-03 12:25 ` Ronald S. Bultje [this message]
2005-03-04 9:15 ` Giuliano Pochini
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=1109852722.2840.51.camel@tux.lan \
--to=rbultje@ronald.bitfreak.net \
--cc=alsa-devel@lists.sourceforge.net \
--cc=perex@suse.cz \
--cc=tiwai@suse.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.