From: Takashi Iwai <tiwai@suse.de>
To: Lennart Poettering <mznyfn@0pointer.de>
Cc: ALSA Development Mailing List <alsa-devel@alsa-project.org>
Subject: Re: If /dev/snd/controlCx EACCES vs. ENODEV mixup
Date: Mon, 26 Nov 2007 07:53:48 +0100 [thread overview]
Message-ID: <s5hir3ppkeb.wl%tiwai@suse.de> (raw)
In-Reply-To: <20071125215300.GA22640@tango.0pointer.de>
At Sun, 25 Nov 2007 22:53:00 +0100,
Lennart Poettering wrote:
>
> On Sun, 25.11.07 22:42, Jaroslav Kysela (perex@perex.cz) wrote:
>
> >
> > On Sun, 25 Nov 2007, Lennart Poettering wrote:
> >
> > > BTW, what's the status of the BTS? Takashi asked me to post all my
> > > issues on the ML instead of on the BTS. So why have the BTS at all?
> > > It's even linked on the alsa-project.org front page under "I found a
> > > bug!", which is a bit misleading. If this Mantis thing is not liked at
> > > all, would it be possible to make some replacement available? Maybe
> > > just use the kernel bugzilla on bugzilla.kernel.org? It's very fast,
> > > and certainly more fun to work with than with Mantis.
> >
> > I prefer BTS but Takashi not. It's matter of personal preference. Mantis
> > is easy maintainable and we have more projects (or packages) not only
> > drivers.
>
> The kernel bugzilla already is used for stuff like klibc and other
> userspace support code for the kernel. I am sure noone would oppose to
> move the complete bug tracking of ALSA to the kernel bz.
The problem is the total lack of man power for debugging.
You'll understand easily if you see too many open bugs. And the bug
report quality isn't always good. Many reports, e.g. about HD-audio
issue, are either too old, irrelevant, or simply unsupported device
(or all of them are mixed up). Only a few of them are really
interesting. But, even filtering them takes too much time.
So, I guess it won't matter whether it's bugzilla or not. Unless
someone sweeps bug entries regularly, BTS can't work properly.
BTW, regarding bugzilla vs mantis. There are a few features that are
missing in mantis. For example, the below are what I'd love to have
vastly:
- properly create a mail per entry
currently mantis mail notification is broken and useless
- has optional status like NEEDINFO or WAIT_FOR_TESTING
so we cannot mark the entries whether a user-action is required or
not, make difficult to filter
Takashi
next prev parent reply other threads:[~2007-11-26 7:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-25 21:03 If /dev/snd/controlCx EACCES vs. ENODEV mixup Lennart Poettering
2007-11-25 21:40 ` Jaroslav Kysela
2007-11-25 21:42 ` Jaroslav Kysela
2007-11-25 21:53 ` Lennart Poettering
2007-11-25 22:10 ` Jaroslav Kysela
2007-11-26 6:53 ` Takashi Iwai [this message]
2007-11-26 7:47 ` Jaroslav Kysela
2007-11-26 7:59 ` Takashi Iwai
2007-11-26 8:24 ` Jaroslav Kysela
2007-11-26 7:55 ` 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=s5hir3ppkeb.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=mznyfn@0pointer.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.