From: Dan Kegel <dank@kegel.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Dedicated kernel bug database
Date: Thu, 19 Dec 2002 18:26:27 -0800 [thread overview]
Message-ID: <3E027FD3.1090906@kegel.com> (raw)
Hanna Linder wrote:
> --On Thursday, December 19, 2002 06:59:30 PM -0500 Pete Zaitcev <zaitcev@redhat.com> wrote:
>
>>> Why are bugs automatically assigned to owners?
>>> If there was an unassigned category that would make it
>>> easy to query.
>>
>> Query for "NEW" status for a component and do not put anything
>> into "owner" fireld.
>
> If there was a NEW field that would be exactly what I was
> asking for. When I do a query the only options I see are: OPEN,
> ASSIGNED, RESOLVED, APPROVED, REJECTED, DEFERRED, CLOSED.
> Where is the NEW? Is there somewhere else to do queries?
When I first looked at the query form, I was overwhelmed by the
list of states. Clicking on the link above the list takes you to
http://bugzilla.kernel.org/queryhelp.cgi#status
which helps a bit. (I'm kind of used to a shorter list of states, e.g.
"new / assigned / verifyfix / closed", but bugzilla's list doesn't
look *too* complicated.)
--
Dan Kegel
Linux User #78045
http://www.kegel.com
next reply other threads:[~2002-12-20 2:10 UTC|newest]
Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-20 2:26 Dan Kegel [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-12-22 18:53 Dedicated kernel bug database Adam J. Richter
2002-12-22 2:50 Hell.Surfers
2002-12-22 9:16 ` John Bradford
2002-12-20 11:18 Nicolas Mailhot
2002-12-19 21:04 Heater, Daniel (IndSys, GEFanuc, VMIC)
[not found] <2CC936747EA1284DA378A18D730697420158A50E@exchacad.ms.gettysburg.edu>
2002-12-19 20:33 ` Justin Pryzby
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
2002-12-19 13:35 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
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-21 2:52 ` 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
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=3E027FD3.1090906@kegel.com \
--to=dank@kegel.com \
--cc=linux-kernel@vger.kernel.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 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.