Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Joe Hsu" <nagual.hsu@gmail.com>
To: Dirk Jagdmann <doj@cubic.org>
Cc: alsa-devel@alsa-project.org
Subject: Re: libaoss.so hole?
Date: Sat, 18 Mar 2006 07:27:02 +0800	[thread overview]
Message-ID: <7fe205990603171527g229fdff1u@mail.gmail.com> (raw)
In-Reply-To: <7fe205990603171520t29c81bag@mail.gmail.com>

A
     And if it will not be that transparent in the future, please add
some comments in the document or it would be a bug caused by the
ignorance of oss application developers and by the in-complete
documnets. And that kind of bug is sometimes not easy to hunt down if
the application is big.

2006/3/18, Joe Hsu <nagual.hsu@gmail.com>:
>    Of course. I know what you mean. But that is like a work around to
> me. And I did a work around too. Since many oss developers didn't
> think about the oss-to-alsa layer, this layer must be as transparent
> as possible.
>    Well, just my own opinion.
> --
> The sun is shinny but the ice is slippery.
>


--
The sun is shinny but the ice is slippery.


-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid\x110944&bid$1720&dat\x121642

  reply	other threads:[~2006-03-17 23:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-17 13:12 libaoss.so hole? Joe Hsu
2006-03-17 16:51 ` Takashi Iwai
2006-03-20  2:18   ` nagual.hsu
2006-03-17 17:49 ` Dirk Jagdmann
2006-03-17 23:20   ` Joe Hsu
2006-03-17 23:27     ` Joe Hsu [this message]
2006-03-20 11:46       ` 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=7fe205990603171527g229fdff1u@mail.gmail.com \
    --to=nagual.hsu@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=doj@cubic.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox