netdev
[Top] [All Lists]

Re: networking bugs and bugme.osdl.org

To: Ben Collins <bcollins@xxxxxxxxxx>
Subject: Re: networking bugs and bugme.osdl.org
From: Andrew Morton <akpm@xxxxxxxxx>
Date: Fri, 27 Jun 2003 16:25:27 -0700
Cc: davidel@xxxxxxxxxxxxxxx, davem@xxxxxxxxxx, mbligh@xxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, linux-net@xxxxxxxxxxxxxxx, netdev@xxxxxxxxxxx
In-reply-to: <20030627213153.GR501@xxxxxxxxxxxxxxx>
References: <20030626.224739.88478624.davem@xxxxxxxxxx> <21740000.1056724453@[10.10.2.4]> <Pine.LNX.4.55.0306270749020.4137@xxxxxxxxxxxxxxxxxxxxxxxxxx> <20030627.143738.41641928.davem@xxxxxxxxxx> <Pine.LNX.4.55.0306271454490.4457@xxxxxxxxxxxxxxxxxxxxxxxxxx> <20030627213153.GR501@xxxxxxxxxxxxxxx>
Sender: netdev-bounce@xxxxxxxxxxx
Ben Collins <bcollins@xxxxxxxxxx> wrote:
>
>  I'm with Dave on this one.

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.

It's irritating replying to a bugzilla entry when you _know_ that you're
cutting other interested parties out of the loop.

And mailing lists tend to be self-correcting:

- The once-off bugs due to broken hardware get filtered away.

- The bugs which simply get magically fixed when someone repaired some
  unrelated part of the kernel get filtered out.

- The bugs which are affecting people the most get reported the most.

- Lots of other people can chip in with potentially useful info.


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.


<Prev in Thread] Current Thread [Next in Thread>