From: Takashi Iwai <tiwai@suse.de>
To: Paul Davis <paul@linuxaudiosystems.com>
Cc: linux-audio-dev@music.columbia.edu,
ardour-dev <ardour-dev@lists.sourceforge.net>,
alsa-devel <alsa-devel@lists.sourceforge.net>
Subject: Re: Re: [linux-audio-dev] Re: why is no-one responding are you all just a bunch of &*^%&^%^& wits???
Date: Thu, 13 Feb 2003 10:44:00 +0100 [thread overview]
Message-ID: <s5h7kc4ms67.wl@alsa2.suse.de> (raw)
In-Reply-To: <E18j00T-0003MM-00@sc8-sf-list1.sourceforge.net>
At Wed, 12 Feb 2003 11:49:08 -0500,
Paul Davis wrote:
>
> when ardour is in a state where i believe (rightly or wrongly) that a
> reasonably typical target user can sit down and just use it without
> encountering bugs when recording a typical 12-32 track piece, there
> will be binaries.
don't forget that the binary distribution may cause different kind of
problems, too.
the binary might not run on different distributions, or even on a
different machine with a same distribution, unless you give
all-static-linked binary. (note that even a binary like netscape 4.x
cannot run properly now with the new glibc because of java.)
and you would likely ignore a bug-report for such, because the only
answer is "it works for me" :)
Takashi (in a pessmistic atmosphere)
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
next prev parent reply other threads:[~2003-02-13 9:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200302121448.h1CEm9j29428@roar.music.columbia.edu>
2003-02-12 16:16 ` [linux-audio-dev] Re: why is no-one responding are you all just a bunch of &*^%&^%^& wits??? ljp
2003-02-12 16:49 ` Paul Davis
2003-02-12 17:56 ` ljp
2003-02-13 9:44 ` Takashi Iwai [this message]
2003-02-13 12:18 ` 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=s5h7kc4ms67.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@lists.sourceforge.net \
--cc=ardour-dev@lists.sourceforge.net \
--cc=linux-audio-dev@music.columbia.edu \
--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 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.