public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Hanna Linder <hannal@us.ibm.com>
To: mbligh@aracnet.com
Cc: Eli Carter <eli.carter@inet.com>,
	"Randy.Dunlap" <rddunlap@osdl.org>,
	linux-kernel@vger.kernel.org
Subject: Re: Dedicated kernel bug database
Date: Thu, 19 Dec 2002 14:45:42 -0800	[thread overview]
Message-ID: <42790000.1040337942@w-hlinder> (raw)
In-Reply-To: <3E0240CA.4000502@inet.com>

> Bug tracking can get much better (I _hope_!), but I expect it to take some beating on the problem.  Keep beating on it.

OK. Since we are on the topic. I have some (intending to be) constructive
criticisms for the owners of the 2.5 kernel tracker site (not sure exactly 
who they are but I know mbligh is part of it).

Why are bugs automatically assigned to owners? 
	If there was an unassigned category that would make it 
	easy to query.
	
How else are those of us who want to help stabilize the 2.5 kernel supposed 
	to know which bugs are being worked on and which are not? 
	(Please dont tell me "email". Am I really supposed to email every 
	person who has a bug asking if they are really working on it or not?)

Could you make a list of all the people who have volunteered to be
	bugtracker maintainers and their respective kernel pieces. 

Also a list of people who arent maintainers but are available to help 
	could be useful for the owners to assign bugs to.

Thanks.

Hanna



  parent reply	other threads:[~2002-12-19 22:31 UTC|newest]

Thread overview: 74+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-19 13:35 Dedicated kernel bug database John Bradford
2002-12-19 17:33 ` Brian Jackson
2002-12-20  3:26   ` Martin J. Bligh
2002-12-19 17:48 ` Eli Carter
2002-12-19 18:49   ` Dave Jones
2002-12-19 19:49     ` Eli Carter
2002-12-19 20:12       ` John Bradford
2002-12-19 20:24         ` Eli Carter
2002-12-19 20:45           ` John Bradford
2002-12-19 19:52     ` John Bradford
2002-12-19 20:18       ` Dave Jones
2002-12-19 20:32         ` Randy.Dunlap
2002-12-19 20:42         ` John Bradford
2002-12-20  3:40           ` Martin J. Bligh
2002-12-20  9:48             ` John Bradford
2002-12-20 10:40               ` Dave Jones
2002-12-20 16:08               ` Martin J. Bligh
2002-12-20  3:35     ` Martin J. Bligh
2002-12-20 17:32       ` Jon Tollefson
2002-12-19 20:09 ` Bill Davidsen
2002-12-19 20:32   ` John Bradford
2002-12-19 21:11     ` Stephen Wille Padnos
2002-12-19 21:40       ` John Bradford
2002-12-19 21:32         ` Randy.Dunlap
2002-12-19 21:55           ` John Bradford
2002-12-19 21:57             ` Eli Carter
2002-12-19 21:55               ` Randy.Dunlap
2002-12-19 22:45               ` Hanna Linder [this message]
2002-12-20  1:39                 ` Martin J. Bligh
2002-12-20  2:01                   ` Hanna Linder
2002-12-20  2:20                     ` Martin J. Bligh
2002-12-20 15:09                       ` Jon Tollefson
2002-12-20 23:52                         ` Hanna Linder
2002-12-21  3:30                           ` Jon Tollefson
2002-12-20 10:35                     ` Dave Jones
2002-12-20 19:37                       ` Hanna Linder
2002-12-20  2:10                   ` Hanna Linder
2002-12-20  2:22                     ` Martin J. Bligh
2002-12-20  2:58                       ` Randy.Dunlap
2002-12-20  3:21                         ` Martin J. Bligh
     [not found]                   ` <31080000.1040418947@w-hlinder>
2002-12-20 21:43                     ` Dedicated kernel bug database + documentaion Hanna Linder
2002-12-20 21:59                       ` Randy.Dunlap
2002-12-20 22:01                         ` Martin J. Bligh
2002-12-20 21:59                       ` Eli Carter
2002-12-21  2:52                     ` Dedicated kernel bug database Martin J. Bligh
2002-12-21  3:27                       ` Jon Tollefson
2002-12-30 21:58                         ` Hanna Linder
     [not found]               ` <mailman.1040338801.24520.linux-kernel2news@redhat.com>
2002-12-19 23:59                 ` Pete Zaitcev
2002-12-20  0:19                   ` Hanna Linder
2002-12-20  0:24                     ` Pete Zaitcev
2002-12-20  1:01                       ` Hanna Linder
2002-12-20 10:32                         ` Dave Jones
2002-12-20 10:41                           ` Russell King
2002-12-20 10:30                     ` Dave Jones
2002-12-20 15:43                       ` Eli Carter
2002-12-19 22:23             ` Stephen Wille Padnos
  -- strict thread matches above, loose matches on Subject: below --
2002-12-19 17:46 Dan Kegel
2002-12-19 18:00 ` John Bradford
2002-12-19 18:08   ` Eli Carter
2002-12-19 20:08     ` John Bradford
2002-12-19 20:38       ` Eli Carter
2002-12-19 20:59         ` John Bradford
2002-12-19 21:14           ` Eli Carter
2002-12-20 14:23           ` Horst von Brand
2002-12-19 22:05         ` Dan Kegel
2002-12-19 22:26         ` Dan Kegel
2002-12-19 23:09           ` John Bradford
     [not found] <2CC936747EA1284DA378A18D730697420158A50E@exchacad.ms.gettysburg.edu>
2002-12-19 20:33 ` Justin Pryzby
2002-12-19 21:04 Heater, Daniel (IndSys, GEFanuc, VMIC)
2002-12-20  2:26 Dan Kegel
2002-12-20 11:18 Nicolas Mailhot
2002-12-22  2:50 Hell.Surfers
2002-12-22  9:16 ` John Bradford
2002-12-22 18:53 Adam J. Richter

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=42790000.1040337942@w-hlinder \
    --to=hannal@us.ibm.com \
    --cc=eli.carter@inet.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mbligh@aracnet.com \
    --cc=rddunlap@osdl.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