From: Takashi Iwai <tiwai@suse.de>
To: James Courtier-Dutton <James@superbug.demon.co.uk>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: ALSA Test suite
Date: Mon, 15 Mar 2004 17:00:39 +0100 [thread overview]
Message-ID: <s5h3c8ahzh4.wl@alsa2.suse.de> (raw)
In-Reply-To: <4055CFA4.4040600@superbug.demon.co.uk>
At Mon, 15 Mar 2004 15:45:40 +0000,
James Courtier-Dutton wrote:
>
> Takashi Iwai wrote:
> >
> >
> > there are test codes in alsa-lib/tests directory.
> > also James Courtier-Dutton wrote some neat test programs (i'd like to
> > include them too).
> >
> > Takashi
> >
>
> Although you have not asked me directly, feel free to include my test
> programs.
oh thanks, it was under evaluation before getting permission ;)
> I assume you are talking about the ones from: -
> http://www.superbug.demon.co.uk/speaker-test/
> Just make sure that my name,copyright message appears at the top of each
> source code file you use.
maybe we'll need a configure setup. i'll work on it later.
the question is to where should it go? in alsa-lib/test, alsa-utils?
of course, if we have the alsa-test tree, it would be the best place.
> Please tell me as soon as they appear in the alsa cvs, because I need to
> remove them from my site due to bandwidth limits.
ok.
ciao,
Takashi
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
next prev parent reply other threads:[~2004-03-15 16:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-14 9:51 ALSA Test suite Jignesh Patel
2004-03-15 10:39 ` Takashi Iwai
2004-03-15 15:45 ` James Courtier-Dutton
2004-03-15 16:00 ` Takashi Iwai [this message]
2004-03-15 18:30 ` Florian Schmidt
2004-03-15 19:11 ` Doug
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=s5h3c8ahzh4.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=James@superbug.demon.co.uk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox