From: "Martin J. Bligh" <mbligh@aracnet.com>
To: Khoa Huynh <khoa@us.ibm.com>, kniht@us.ibm.com
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
"David S. Miller" <davem@redhat.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
mailing-lists@digitaleric.net, Jeff Garzik <jgarzik@pobox.com>
Subject: Re: Bugzilla bug tracking database for 2.5 now available.
Date: Fri, 15 Nov 2002 12:28:41 -0800 [thread overview]
Message-ID: <326030000.1037392121@flay> (raw)
In-Reply-To: <OFF50CC956.56290AFD-ON85256C72.005E479D@pok.ibm.com>
> A way to get around this is to create 3-level component list (as opposed
> to 2-level currently: category and components). This 3-level component
> list would go like this:
>
> Product --> Category --> Component
I'm not sure we really want this to be 3-level as that'd involve
replicating all the categories underneath. The OpSys field type
suggestion as an independant field would be nice, but the Bugzilla
code will need some tweaking to support possibly different default
owners dependant on that field.
For now, Jon has created us an "Alternate trees" category, with "ac"
and "mm" components, with appropriate text in the template to encourage
people to file bugs that happen (only) on those trees under the
"tree-specific" categories, and we can move bugs out from there if
need be. Hopefully that will make people happier for now, there may
be a cleaner solution long-term, but that needs more thought and more
work.
M.
next prev parent reply other threads:[~2002-11-15 19:28 UTC|newest]
Thread overview: 94+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-15 17:21 Bugzilla bug tracking database for 2.5 now available Khoa Huynh
2002-11-15 20:28 ` Martin J. Bligh [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-11-18 22:47 Khoa Huynh
2002-11-18 17:19 Khoa Huynh
2002-11-18 16:11 Khoa Huynh
2002-11-16 0:49 Khoa Huynh
2002-11-16 0:41 Khoa Huynh
2002-11-15 23:07 Khoa Huynh
2002-11-15 23:24 ` Martin J. Bligh
2002-11-15 22:34 Khoa Huynh
2002-11-15 22:59 ` Jeff Garzik
2002-11-15 23:21 ` Martin J. Bligh
2002-11-16 0:07 ` Jeff Garzik
[not found] <396026666.1037298946@[10.10.2.3].suse.lists.linux.kernel>
[not found] ` <1037395835.22209.3.camel@rth.ninka.net.suse.lists.linux.kernel>
[not found] ` <336460000.1037398316@flay.suse.lists.linux.kernel>
[not found] ` <20021115.133004.65979948.davem@redhat.com.suse.lists.linux.kernel>
2002-11-15 21:50 ` Andi Kleen
2002-11-15 21:58 ` David S. Miller
2002-11-15 22:25 ` Martin J. Bligh
2002-11-15 21:25 Khoa Huynh
2002-11-15 22:18 ` Martin J. Bligh
2002-11-15 16:23 Khoa Huynh
2002-11-15 16:32 ` Larry McVoy
[not found] <fa.cg3ae9v.ji8118@ifi.uio.no>
[not found] ` <fa.i6a51vv.5s3if@ifi.uio.no>
2002-11-15 10:58 ` FZiegler
2002-11-15 7:22 Khoa Huynh
2002-11-15 16:00 ` Jeff Garzik
2002-11-15 19:07 ` Martin J. Bligh
2002-11-15 6:33 Michael D. Crawford
2002-11-14 22:44 Nicolas Mailhot
2002-11-15 2:03 ` David S. Miller
2002-11-15 2:35 ` Martin J. Bligh
2002-11-15 2:51 ` Andrew Morton
2002-11-15 3:43 ` Thomas Molina
2002-11-15 3:46 ` Brad Hards
2002-11-15 3:50 ` Andrew Morton
2002-11-15 3:58 ` Patrick Finnegan
2002-11-16 3:01 ` john slee
2002-11-15 2:53 ` Eric Northup
2002-11-15 15:15 ` Alan Cox
2002-11-15 15:41 ` Paul Larson
2002-11-15 15:44 ` Martin J. Bligh
2002-11-15 16:49 ` Jon Tollefson
2002-11-15 16:43 ` Jason Lunz
2002-11-15 7:11 ` David S. Miller
2002-11-15 15:31 ` Larry McVoy
2002-11-15 9:40 ` Lars Marowsky-Bree
2002-11-15 21:30 ` David S. Miller
2002-11-15 22:11 ` Martin J. Bligh
2002-11-15 21:23 ` Larry McVoy
2002-11-15 21:33 ` David S. Miller
2002-11-16 7:10 ` Gerhard Mack
2002-11-16 7:17 ` Arnaldo Carvalho de Melo
2002-11-16 21:08 ` Murray J. Root
2002-11-16 21:41 ` Arnaldo Carvalho de Melo
2002-11-16 21:44 ` Martin J. Bligh
2002-11-16 21:52 ` Arnaldo Carvalho de Melo
2002-11-16 22:01 ` Murray J. Root
2002-11-16 21:54 ` Jeff Garzik
2002-11-16 22:00 ` Arnaldo Carvalho de Melo
2002-11-15 21:30 ` David S. Miller
2002-11-15 22:22 ` Martin J. Bligh
2002-11-17 19:33 ` David S. Miller
2002-11-18 2:30 ` Martin J. Bligh
2002-11-18 2:31 ` Werner Almesberger
2002-11-18 4:46 ` Oliver Xymoron
2002-11-18 5:58 ` Werner Almesberger
2002-11-18 7:52 ` Martin J. Bligh
2002-11-18 16:53 ` Eli Carter
2002-11-18 17:04 ` Oliver Xymoron
2002-11-15 2:52 ` Jeff Garzik
2002-11-14 2:33 Martin J. Bligh
2002-11-14 17:01 ` Jeff Garzik
2002-11-14 18:04 ` Martin J. Bligh
2002-11-14 20:11 ` David S. Miller
2002-11-14 20:12 ` Arnaldo Carvalho de Melo
2002-11-14 22:57 ` Martin J. Bligh
2002-11-14 22:08 ` Arnaldo Carvalho de Melo
2002-11-14 23:22 ` Martin J. Bligh
2002-11-15 1:26 ` David S. Miller
2002-11-14 17:04 ` Jeff Garzik
2002-11-14 18:21 ` Martin J. Bligh
2002-11-14 18:57 ` Timothy D. Witham
[not found] ` <mailman.1037294313.19087.linux-kernel2news@redhat.com>
2002-11-14 19:12 ` Pete Zaitcev
2002-11-14 20:55 ` Martin J. Bligh
2002-11-14 19:36 ` Jeff Garzik
2002-11-14 19:43 ` Pete Zaitcev
2002-11-14 19:48 ` Jeff Garzik
2002-11-14 20:30 ` Jeff Garzik
2002-11-14 23:04 ` Martin J. Bligh
2002-11-14 21:05 ` Jeff Garzik
2002-11-14 21:42 ` Paul Larson
2002-11-14 22:09 ` Robert Love
2002-11-15 15:06 ` Petr Baudis
[not found] ` <mailman.1037373001.29912.linux-kernel2news@redhat.com>
2002-11-15 16:48 ` Pete Zaitcev
2002-11-15 19:11 ` Martin J. Bligh
2002-11-15 1:49 ` Chris Friesen
2002-11-16 19:46 ` Robert Love
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=326030000.1037392121@flay \
--to=mbligh@aracnet.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=davem@redhat.com \
--cc=jgarzik@pobox.com \
--cc=khoa@us.ibm.com \
--cc=kniht@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mailing-lists@digitaleric.net \
/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