All of lore.kernel.org
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@davemloft.net>
To: ultralinux@vger.kernel.org
Subject: Re: Please review the sparc64 bugs in the kernel Bugzilla
Date: Thu, 01 Sep 2005 23:48:31 +0000	[thread overview]
Message-ID: <20050901.164831.129514045.davem@davemloft.net> (raw)
In-Reply-To: <20050901002932.GB3766@stusta.de>

From: Adrian Bunk <bunk@stusta.de>
Date: Fri, 2 Sep 2005 01:34:01 +0200

> May I ask why?

Because I shouldn't have to spend time on some bugzilla web site just
to work on some bug.  The bugs should come to me, by being reported to
the appropriate mailing list, I shouldn't have to seek them.

The kernel bugzilla exists only to make some bean counters at some
corporations happy that there is some place to track kernel bugs.  But
this is wholly incompatible with how upstream kernel development
works.  The kernel bugzilla database would never have been created
with the sole impetus of the core kernel folks, that's simply not how
we work.

That is why.

Sending bugzilla reports directly to the list is not the answer.
That means a lot of garbage ends up on the list, so if anything
it should either:

1) get forwarded by hand by someone willing to volunteer to
   filter out the crap
2) get sent directly to the right mailing list in the first
   place, bypassing the kernel bugzilla altogether

The latter is what happens in practice for sparc stuff.

  parent reply	other threads:[~2005-09-01 23:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-01  0:29 Please review the sparc64 bugs in the kernel Bugzilla Adrian Bunk
2005-09-01  1:40 ` David S. Miller
2005-09-01 23:34 ` Adrian Bunk
2005-09-01 23:48 ` David S. Miller [this message]
2005-09-02 22:34 ` Adrian Bunk

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=20050901.164831.129514045.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=ultralinux@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.