From: Larry McVoy <lm@bitmover.com>
To: "David S. Miller" <davem@redhat.com>
Cc: greearb@candelatech.com, davidel@xmailserver.org,
mbligh@aracnet.com, linux-kernel@vger.kernel.org,
linux-net@vger.kernel.org, netdev@oss.sgi.com
Subject: Re: networking bugs and bugme.osdl.org
Date: Fri, 27 Jun 2003 17:19:54 -0700 [thread overview]
Message-ID: <20030628001954.GD18676@work.bitmover.com> (raw)
In-Reply-To: <20030627.170022.74744550.davem@redhat.com>
On Fri, Jun 27, 2003 at 05:00:22PM -0700, David S. Miller wrote:
> From: Ben Greear <greearb@candelatech.com>
> Date: Fri, 27 Jun 2003 15:36:30 -0700
>
> So, you'd be happy so long as bugz sent mail to the netdev mailing
> lists instead of to you?
>
> The best power I have to scale is the delete key in my email
> reader, when I delete an email it's gone and that's it.
>
> bugme bugs don't have this attribute, they are like emails that
> persist forever until someone does something about them, and this is
> the big problem I have with it.
I've proposed this before and nobody listened but maybe this time...
I think what you want is a bug database which distinguishes between
filed bugs and reviewed bugs. You want to capture all bug reports,
as Alan says (he's right, there is no question about it, you need to
capture the data). You also want an *automatic* way for bugs to just
rot. Anyone can file a bug but unless someone with expertise in the
area reviews the bug and agrees to do something about it, the bug rots.
It's level 1 (capture) and level 2 (we really need to do something about
this some day). Level 1 will have zillions of duplicates and tons of
other noise. Level 2 should be a small list, no duplicates, carefully
managed.
--
---
Larry McVoy lm at bitmover.com http://www.bitmover.com/lm
next prev parent reply other threads:[~2003-06-28 0:19 UTC|newest]
Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-27 5:30 networking bugs and bugme.osdl.org David S. Miller
2003-06-27 5:46 ` Martin J. Bligh
2003-06-27 5:47 ` David S. Miller
2003-06-27 7:59 ` Matti Aarnio
2003-06-27 8:00 ` David S. Miller
2003-06-27 15:00 ` Martin J. Bligh
2003-06-27 14:34 ` Martin J. Bligh
2003-06-27 14:56 ` Davide Libenzi
2003-06-27 21:37 ` David S. Miller
2003-06-27 21:54 ` Ben Greear
2003-06-27 21:54 ` David S. Miller
2003-06-27 22:15 ` Ben Greear
2003-06-27 22:19 ` David S. Miller
2003-06-27 22:36 ` Ben Greear
2003-06-28 0:00 ` David S. Miller
2003-06-28 0:15 ` Martin J. Bligh
2003-06-28 0:32 ` David S. Miller
2003-06-28 0:19 ` Larry McVoy [this message]
2003-06-28 0:27 ` Martin J. Bligh
2003-06-28 19:20 ` Alan Cox
2003-06-29 0:44 ` Martin J. Bligh
2003-06-27 23:08 ` Alan Cox
2003-06-28 0:21 ` David S. Miller
2003-06-28 19:19 ` Alan Cox
2003-06-28 22:03 ` David S. Miller
2003-06-28 23:15 ` Alan Cox
2003-06-28 23:20 ` David S. Miller
2003-06-28 23:46 ` Alan Cox
2003-07-12 17:07 ` Jan Rychter
2003-07-13 5:22 ` David S. Miller
2003-07-13 5:42 ` Jan Rychter
2003-06-27 23:12 ` Martin J. Bligh
2003-06-27 22:02 ` Davide Libenzi
2003-06-27 21:31 ` Ben Collins
2003-06-27 23:25 ` Andrew Morton
2003-06-27 22:30 ` Ben Collins
2003-06-28 0:32 ` Larry McVoy
2003-06-28 19:26 ` Alan Cox
2003-06-28 0:38 ` Martin J. Bligh
2003-06-28 1:14 ` Andrew Morton
2003-06-28 2:13 ` Martin J. Bligh
2003-06-28 2:35 ` Andrew Morton
2003-06-28 6:08 ` Martin J. Bligh
2003-06-28 3:27 ` Jamal Hadi
2003-06-27 22:02 ` David S. Miller
2003-06-27 22:11 ` Davide Libenzi
2003-06-27 22:13 ` David S. Miller
2003-06-27 18:50 ` Ben Greear
2003-06-27 21:44 ` David S. Miller
2003-06-27 22:47 ` Martin J. Bligh
2003-06-27 22:53 ` Larry McVoy
2003-06-28 0:44 ` David S. Miller
2003-06-28 0:09 ` David S. Miller
2003-06-27 23:04 ` Alan Cox
2003-06-28 0:19 ` David S. Miller
2003-06-29 21:15 ` David S. Miller
2003-06-29 21:45 ` Andries Brouwer
2003-06-29 21:51 ` David S. Miller
2003-06-29 22:49 ` Andries Brouwer
2003-06-29 23:21 ` Davide Libenzi
2003-06-29 22:07 ` Alan Cox
2003-06-29 22:13 ` David S. Miller
2003-06-30 2:35 ` Martin J. Bligh
2003-07-20 16:46 ` Petr Baudis
-- strict thread matches above, loose matches on Subject: below --
2003-06-27 15:25 John Bradford
2003-06-28 8:00 John Bradford
2003-06-28 8:10 John Bradford
2003-06-28 22:37 John Bradford
2003-06-29 22:28 John Bradford
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=20030628001954.GD18676@work.bitmover.com \
--to=lm@bitmover.com \
--cc=davem@redhat.com \
--cc=davidel@xmailserver.org \
--cc=greearb@candelatech.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@vger.kernel.org \
--cc=mbligh@aracnet.com \
--cc=netdev@oss.sgi.com \
/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;
as well as URLs for NNTP newsgroup(s).