From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: "David S. Miller" <davem@redhat.com>
Cc: greearb@candelatech.com, mbligh@aracnet.com,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-net@vger.kernel.org, netdev@oss.sgi.com
Subject: Re: networking bugs and bugme.osdl.org
Date: 28 Jun 2003 00:04:30 +0100 [thread overview]
Message-ID: <1056755070.5463.12.camel@dhcp22.swansea.linux.org.uk> (raw)
In-Reply-To: <20030627.144426.71096593.davem@redhat.com>
On Gwe, 2003-06-27 at 22:44, David S. Miller wrote:
> This work for kernel patches, and has so for over 5 years.
> So what makes anyone thing it doesn't work for bug reporting?
It works badly for kernel patches, stuff does get lost forever, missed
etc. Having it all archived somewhere is really valuable because it
means you can spot patterns, trends and also when someone who isnt a
hacker hits the bug *they* can find the patch you missed and send it on
or remind you
You are assuming there is a relationship in bug severity/commonness and
number of *developers* who hit it. That isnt true, developer and end
user hardware patterns are radically different in some areas
next prev parent reply other threads:[~2003-06-27 22:53 UTC|newest]
Thread overview: 73+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-27 5:30 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
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 [this message]
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=1056755070.5463.12.camel@dhcp22.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=davem@redhat.com \
--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
all inboxes | Powered by JetHome®