From: Patrick Shirkey <pshirkey@boosthardware.com>
To: Paul Davis <paul@linuxaudiosystems.com>
Cc: alsa-devel <alsa-devel@lists.sourceforge.net>
Subject: Re: Parsing asoundrc for devices.
Date: Thu, 27 Feb 2003 03:18:17 +0900 [thread overview]
Message-ID: <3E5D04E9.7020900@boosthardware.com> (raw)
In-Reply-To: E18o5v3-0002n9-00@sc8-sf-list1.sourceforge.net
Paul Davis wrote:
>>I don't quite follow this. Is that a fictional call which an app could
>>use to get these details or is it an already functioning piece of code
>>that I haven't seen in action?
>
>
> the latter.
>
Sorry to be lame but...
Does anyone know if it is used in any apps that I might have in my
system or have I not seen it in action because no one uses it yet?
--
Patrick Shirkey - Boost Hardware Ltd.
Http://www.boosthardware.com
Http://www.djcj.org - The Linux Audio Users guide
========================================
Being on stage with the band in front of crowds shouting, "Get off! No!
We want normal music!", I think that was more like acting than anything
I've ever done.
Goldie, 8 Nov, 2002
The Scotsman
-------------------------------------------------------
This SF.net email is sponsored by: Scholarships for Techies!
Can't afford IT training? All 2003 ictp students receive scholarships.
Get hands-on training in Microsoft, Cisco, Sun, Linux/UNIX, and more.
www.ictp.com/training/sourceforge.asp
next prev parent reply other threads:[~2003-02-26 18:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200302261718.h1QHIHT23001@www2.webhosting.cx>
2003-02-26 17:41 ` Parsing asoundrc for devices Patrick Shirkey
2003-02-26 18:07 ` Paul Davis
2003-02-26 18:18 ` Patrick Shirkey [this message]
2003-02-26 20:57 ` Jaroslav Kysela
2003-02-26 16:20 Patrick Shirkey
2003-02-26 17:20 ` Paul Davis
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=3E5D04E9.7020900@boosthardware.com \
--to=pshirkey@boosthardware.com \
--cc=alsa-devel@lists.sourceforge.net \
--cc=paul@linuxaudiosystems.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox