From: Chip Salzenberg <chip@pobox.com>
To: alsa-devel@lists.sourceforge.net
Subject: "Missing, Reward Offered: /proc/asound/dev"
Date: Fri, 16 May 2003 16:50:18 -0400 [thread overview]
Message-ID: <20030516205018.GI7921@perlsupport.com> (raw)
OK, I'm in the habit of playing with the CVS drivers, and of course
when it breaks it's my own fault, and that's fine ... but:
Today I see in CVS that the "/proc/asound/dev" directory is not just
temporarily broken; its support has been entirely removed. Now none
of my alsa apps (well, OK, I only have two) are happy, nor do they
have any prospect of being happy in the future.
Can I get a "WTF?" from the congregation?! Amen!
--
Chip Salzenberg - a.k.a. - <chip@pobox.com>
"I wanted to play hopscotch with the impenetrable mystery of existence,
but he stepped in a wormhole and had to go in early." // MST3K
-------------------------------------------------------
This SF.net email is sponsored by: If flattening out C++ or Java
code to make your application fit in a relational database is painful,
don't do it! Check out ObjectStore. Now part of Progress Software.
http://www.objectstore.net/sourceforge
next reply other threads:[~2003-05-16 20:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-16 20:50 Chip Salzenberg [this message]
2003-05-19 9:28 ` "Missing, Reward Offered: /proc/asound/dev" Takashi Iwai
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=20030516205018.GI7921@perlsupport.com \
--to=chip@pobox.com \
--cc=alsa-devel@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.