netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@redhat.com>
To: Jan Rychter <jan@rychter.com>
Cc: linux-net@vger.kernel.org, linux-kernel@vger.kernel.org,
	netdev@oss.sgi.com
Subject: Re: networking bugs and bugme.osdl.org
Date: Sat, 12 Jul 2003 22:22:22 -0700	[thread overview]
Message-ID: <20030712222222.01089864.davem@redhat.com> (raw)
In-Reply-To: <m2vfu765cx.fsf@tnuctip.rychter.com>

On Sat, 12 Jul 2003 10:07:42 -0700
Jan Rychter <jan@rychter.com> wrote:

> Interesting you should think you're 'rewarding' people. I thought your
> goal was to have fun working on cool software and making it
> better. I also thought I had the same goal as a bug-reporter.
> 
> When I write software, I care about every bug report and consider people
> doing the reporting a very valuable resource.

The whole game changes when you are stretched as thinly
as I am.  Scaling becomes everything, and nitpicking through
vague and poorly composed bug reports is an absolute waste of
my time as networking subsystem maintainer.

If other people want to improve bug reports, put them into
a cute usable database, and munge them along, that's fine with
me.

But _I_ only want to work with things that make the best use
of my limited time.

To be frank and honest, I do things that interest _ME_.  And waddling
through poorly made bug reports is anything but interesting, in fact
it's frustrating work.  I'd rather implement a software 802.11 stack
or TCP Vegas implementation, THAT is what is a good use of my time
because of my knowledge of how all these kinds of things work in the
Linux networking.  I can do things overnight that would take others
weeks.

Having me pillage through a bug database is a poor use of my time and
capabilities.  And all of my time is spent reviewing patches and
dealing with the properly composed bug reports anyways, so even if I
enjoyed pillaging through badly made bug reports I couldn't.

People are assuming that just because _I_ don't want to work on the
bad bug reports that I think nobody should.  It's the exact opposite.

I can't force other people to do or not do things anyways, just like
everyone trying to somehow make it my "duty" to look at every single
bug report cannot force me to do that.

  reply	other threads:[~2003-07-13  5:22 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
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 [this message]
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=20030712222222.01089864.davem@redhat.com \
    --to=davem@redhat.com \
    --cc=jan@rychter.com \
    --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).