All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jack O'Quin" <joq@io.com>
To: Peter L Jones <peter@drealm.org.uk>
Cc: Takashi Iwai <tiwai@suse.de>,
	Karsten Wiese <annabellesgarden@yahoo.de>,
	alsa-devel@lists.sourceforge.net
Subject: Re: snd_ prefix for module options
Date: 10 Oct 2002 11:11:06 -0500	[thread overview]
Message-ID: <87u1juxoit.fsf@sulphur.joq.us> (raw)
In-Reply-To: <200210091937.05652@advent.drealm.org.uk>


Peter L Jones <peter@drealm.org.uk> writes:

> I think it's not so nice.  Anyone running ALSA 0.9 should know it's
> not a "release" version and be happy to have (some breakage).  If
> all that's needed is a quick edit of modules.conf, it shouldn't
> cause too many power-users grief.  Those using distro upgrade tools
> should let their distro maintainer sort it out for them.

This whole thread makes no sense to me at all.

Can someone please explain what terrible problem we're trying to solve
that justifies introducing *any* breakage at all?

I don't mean to single out Peter for this one statement.  But, I am
totally frustrated with the attitude that ALSA is only for power users
and that it's OK to introduce spurious incompatibilities on a whim.

The excuse that 0.9 is not a "release" is wearing thin these days.
Since 0.5, which *is* a release, is "no longer supported", what are
ordinary users expected to run?  OSS?

ALSA is part of the 2.5 kernel now.  It is mainstream Linux software,
good technology, needed by many users.  Isn't it about time to start
thinking and acting that way?
-- 
  Jack O'Quin
  Austin, Texas, USA



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf

  reply	other threads:[~2002-10-10 16:11 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-08 14:04 snd_ prefix for module options Takashi Iwai
2002-10-08 18:14 ` Peter L Jones
2002-10-08 19:35 ` Florian Bomers
2002-10-09  0:48   ` Florian Bomers
2002-10-08 22:44 ` Chris Rankin
2002-10-09  6:03   ` Jaroslav Kysela
2002-10-09  8:48     ` Takashi Iwai
2002-10-09  9:02     ` Chris Rankin
2002-10-09 10:33       ` Jaroslav Kysela
2002-10-09  8:47 ` Clemens Ladisch
2002-10-09 10:15 ` Karsten Wiese
2002-10-09 10:19   ` Takashi Iwai
2002-10-09 17:31     ` Jack O'Quin
2002-10-09 17:41     ` Florian Bomers
2002-10-10 11:46       ` Takashi Iwai
2002-10-09 18:37     ` Peter L Jones
2002-10-10 16:11       ` Jack O'Quin [this message]
2002-10-10 18:49         ` Peter L Jones
2002-10-10 21:18         ` Florian Bomers
2002-10-11 14:15         ` Takashi Iwai
2002-10-11 19:33           ` Jack O'Quin
2002-10-12  8:56             ` Jaroslav Kysela
2002-10-12 17:22               ` Jack O'Quin

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=87u1juxoit.fsf@sulphur.joq.us \
    --to=joq@io.com \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=annabellesgarden@yahoo.de \
    --cc=peter@drealm.org.uk \
    --cc=tiwai@suse.de \
    /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.