public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Dave Jones <davej@redhat.com>
Cc: "Martin J. Bligh" <mbligh@mbligh.org>, Jens Axboe <axboe@suse.de>,
	Andrew Morton <akpm@osdl.org>,
	James.Bottomley@SteelEye.com, linux-kernel@vger.kernel.org
Subject: Re: kernel bugzilla
Date: Mon, 20 Jun 2005 13:58:10 +0200	[thread overview]
Message-ID: <s5hwtopp7e5.wl%tiwai@suse.de> (raw)
In-Reply-To: <20050618191341.GA30620@redhat.com>

At Sat, 18 Jun 2005 15:13:41 -0400,
Dave Jones wrote:
> 
> One of the problems faced by bug-reporters sometimes is that with
> the multitude of bugzillas out there, and no cooperation between
> them all, they don't know where to file their bug.
> "My sound driver blew up, where do I file a bug"
> bugzilla.redhat.com? bugme.osdl.org ? (in fact, I think the ALSA
> folks have their own bugzilla if memory serves correctly)
> [This demonstrates the problem -- even _I_ don't know, and I get a fair
>  amount of alsa bug reports from end-users]

Yes, we have Mantis as own bugtracking system:

	https://bugtrack.alsa-project.org/alsa-bug/

I fully agree with Dave.  There are too many bugzillas, and developers
can't cover all of them, too.

It'd be nice if these (exported) bugzilla systems can notify to the
corresponding devel ML, e.g. alsa-devel in the case of ALSA, so that
the reports surely reach to developers.


Takashi

  parent reply	other threads:[~2005-06-20 12:01 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20050617001330.294950ac.akpm@osdl.org>
     [not found] ` <1119016223.5049.3.camel@mulgrave>
     [not found]   ` <20050617142225.GO6957@suse.de>
2005-06-17 21:10     ` kernel bugzilla Andrew Morton
2005-06-17 21:23       ` Jens Axboe
2005-06-17 21:39         ` Andrew Morton
2005-06-18 14:50           ` Alexey Dobriyan
2005-06-18 18:23             ` Andrew Morton
2005-06-20 18:59               ` Alexey Dobriyan
2005-06-18 15:45           ` Adrian Bunk
2005-06-18 15:58             ` Martin J. Bligh
2005-06-17 21:45         ` Martin J. Bligh
2005-06-18 19:13           ` Dave Jones
2005-06-19  2:54             ` Kyle Moffett
2005-06-19  8:22               ` Dave Jones
2005-06-19 16:58                 ` Kyle Moffett
2005-06-20 11:58             ` Takashi Iwai [this message]
2005-06-20 14:08               ` Martin J. Bligh
2005-06-18  1:14         ` Herbert Xu
2005-06-19 19:02 Kenneth Parrish
  -- strict thread matches above, loose matches on Subject: below --
2003-05-12 23:04 Andrew Morton
2003-05-13 21:55 ` Diego Calleja García

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=s5hwtopp7e5.wl%tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=James.Bottomley@SteelEye.com \
    --cc=akpm@osdl.org \
    --cc=axboe@suse.de \
    --cc=davej@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mbligh@mbligh.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