From: "Martin J. Bligh" <mbligh@aracnet.com>
To: Andrew Morton <akpm@digeo.com>, Ben Collins <bcollins@debian.org>
Cc: davidel@xmailserver.org, davem@redhat.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:38:45 -0700 [thread overview]
Message-ID: <35240000.1056760723@[10.10.2.4]> (raw)
In-Reply-To: <20030627162527.714091ce.akpm@digeo.com>
> I also. The bug database tries to convert the traditional many<->many
> debugging process into a one<->one process. This surely results in a
> lower cleanup rate.
I think your suggestion of sending new bugs out to LKML has made a big
dent in the one<->one problem already. Replacing all the default owner
fields with mailing lists (either existing ones or new ones) instead of
individuals would be another step in that direction, though there may
be a few hurdles to deal with on the way to that.
Yes, we probably also need an "email back in" interface as we've
discussed before to take it up to many-many.
> It is nice to have a record. But bugzilla is not a comfortable or
> productive environment within which to drill down into and fix problems.
OK ... But I'd rather try to fix it than to throw the baby out with the
bath water. I don't believe it's "unfixable" - the concept of tracking
bugs / problems and making sure they're closed out still seems sound to me.
As an example, I've seen several examples already where I've pestered
people about bugs that already had patches attatched to them that resulted
in "oh, yeah, I forgot to actually submit that", and it's got fixes back
into mainline. I find it somewhat hard to believe that just about every
other big project (including open source ones) uses some form of bug
tracking system, and yet Linux is somehow magically different ;-)
M.
next prev parent reply other threads:[~2003-06-28 0:27 UTC|newest]
Thread overview: 73+ 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
2003-06-28 0:27 ` Martin J. Bligh
2003-06-28 19:20 ` Alan Cox
2003-06-29 0:40 ` Daniel Jacobowitz
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 4:15 ` Greg KH
2003-07-14 20:25 ` USB bugs (was: networking bugs and bugme.osdl.org) Jan Rychter
[not found] ` <20030714230236.GA7195@kroah.com>
2003-07-15 20:24 ` Jan Rychter
2003-07-13 5:22 ` networking bugs and bugme.osdl.org David S. Miller
2003-07-13 5:42 ` Jan Rychter
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 [this message]
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
2003-06-27 15:25 John Bradford
2003-06-27 16:18 Nicolas Mailhot
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='35240000.1056760723@[10.10.2.4]' \
--to=mbligh@aracnet.com \
--cc=akpm@digeo.com \
--cc=bcollins@debian.org \
--cc=davem@redhat.com \
--cc=davidel@xmailserver.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@vger.kernel.org \
--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).