From: Takashi Iwai <tiwai@suse.de>
To: Jaroslav Kysela <perex@suse.cz>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: Standard PCM name?
Date: Thu, 13 Jan 2005 16:48:54 +0100 [thread overview]
Message-ID: <s5hvfa1ib2x.wl@alsa2.suse.de> (raw)
In-Reply-To: <Pine.LNX.4.58.0501131643310.2088@pnote.perex-int.cz>
At Thu, 13 Jan 2005 16:43:53 +0100 (CET),
Jaroslav wrote:
>
> On Thu, 13 Jan 2005, Takashi Iwai wrote:
>
> > Any comments? Better names?
>
> cdefault ?
I thought of an alike, but I feel it's a bit too long and too similar
with default.
Just a question of taste, though.
Takashi
-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
next prev parent reply other threads:[~2005-01-13 15:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-13 13:59 Standard PCM name? Takashi Iwai
2005-01-13 15:43 ` Jaroslav Kysela
2005-01-13 15:48 ` Takashi Iwai [this message]
2005-01-14 11:30 ` Martin Habets
2005-01-14 12:06 ` 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=s5hvfa1ib2x.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@lists.sourceforge.net \
--cc=perex@suse.cz \
/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