From: Florian Faber <faber@faberman.de>
To: alsa-devel@alsa-project.org
Subject: Re: Documentation Request
Date: Wed, 04 Sep 2013 10:18:33 +0200 [thread overview]
Message-ID: <5226ECD9.7060202@faberman.de> (raw)
In-Reply-To: <CAPOzVs5XUZ8RvcC4wTRp1sYZz7PP4UjnKu=qUzUcwdHkB-ta6Q@mail.gmail.com>
Carl,
> Thanks for your response, but I think that is a very poor solution. [ignorant blah]
>
> Surely an experienced core ALSA developer could create such a demo [more blah]
How about: You write the documentation, given your 'fresh' experience
with ALSA to help others in your situation.
Or even better: Accept recommendations from other developers and use
jack. You would have finished after half an hour and your application
would cooperate with all other audio applications.
All you have now is two wasted weeks of your life span and a
non-cooperative application. And other new ALSA users are still in the
same situation as you were.
Flo
--
Machines can do the work, so people have time to think.
public key 8D073185 x-hkp://subkeys.pgp.net
next prev parent reply other threads:[~2013-09-04 8:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-04 0:32 Documentation Request Carl Canuck
2013-09-04 0:58 ` Eliot Blennerhassett
2013-09-04 1:45 ` Carl Canuck
[not found] ` <CACckToUBiwJg1TUMuw3eFws_rvf9qc3ZPfSzy7MRCB8b0JEnRg@mail.gmail.com>
[not found] ` <CAPOzVs4+Sd=UXZ3gMGSNwMk1EW_yKPK+7dTo_vuWD_acyrWw6g@mail.gmail.com>
2013-09-04 3:15 ` Carl Canuck
2013-09-04 6:04 ` Felix Homann
2013-09-04 7:58 ` Clemens Ladisch
2013-09-04 8:18 ` Florian Faber [this message]
2013-09-04 13:20 ` Carl Canuck
2013-09-04 14:04 ` Felix Homann
2013-09-04 14:05 ` Clemens Ladisch
2013-09-04 14:30 ` Carl Canuck
2013-09-04 17:21 ` Joël Krähemann
2013-09-05 12:13 ` Keith A. Milner
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=5226ECD9.7060202@faberman.de \
--to=faber@faberman.de \
--cc=alsa-devel@alsa-project.org \
/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.