All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@codemonkey.org.uk>
To: Valdis.Kletnieks@vt.edu
Cc: linux-kernel@vger.kernel.org
Subject: Re: lkml, bugme.osdl.org?
Date: Tue, 3 Dec 2002 12:15:21 +0000	[thread overview]
Message-ID: <20021203121521.GB30431@suse.de> (raw)
In-Reply-To: <200212030724.gB37O4DL001318@turing-police.cc.vt.edu>

On Tue, Dec 03, 2002 at 02:24:04AM -0500, Valdis.Kletnieks@vt.edu wrote:
 > Out of curiosity, is it preferred that if bugs/patches get found, that they
 > be posted here, to the Bugzilla database, or both?  I've been putting them
 > at both places, so there's discussion here and a history there...

- simple things like compile errors
  here. no need to clog up bugzilla with lots of trivial things.

- architecture xxx doesn't compile
  there's a few of these now in bugzilla, and personally I don't think
  they belong there. Any arch other than i386 is always going to be
  playing catchup, and is nearly always out of date in mainline.

- trivial patches
  send to rusty, cc here.

- anything else
  here. if you don't get a quick-fix, bugzilla it too.
  this way important bugs won't get lost amongst the archives.
  (as long as bugzilla remains usable)

whilst on the subject of bugzilla:
a few people (myself included) go through the bug database once a week
or so pruning out-of-date/fixed entries. So far the ones I've closed have
been quite sensible, but there are a few there of the form..

"xxx doesn't work in 2.5.47", then Rusty's module rewrite happened,
and the tester didn't (or couldn't) see if it got fixed in subsequent
kernels. I'll send out pings to such reports when they get to something
like 5 kernels old. If the problem then doesn't get re-ACKed, I'll
close it. Any objections?

		Dave

-- 
| Dave Jones.        http://www.codemonkey.org.uk
| SuSE Labs

  reply	other threads:[~2002-12-03 12:10 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-03  7:24 lkml, bugme.osdl.org? Valdis.Kletnieks
2002-12-03 12:15 ` Dave Jones [this message]
2002-12-03 14:13   ` bill davidsen
2002-12-03 18:09   ` Tupshin Harper
2002-12-04 11:58   ` Dr. David Alan Gilbert
2002-12-04 12:35     ` Russell King
2002-12-04 12:42     ` Dave Jones
2002-12-04 18:32       ` Dr. David Alan Gilbert
2002-12-04 22:20         ` Russell King
2002-12-05  9:15           ` David Woodhouse
2002-12-05  9:25             ` William Lee Irwin III
2002-12-05  9:34               ` David Woodhouse
2002-12-05  9:35                 ` William Lee Irwin III
2002-12-05 14:24       ` bill davidsen
2002-12-03 20:33 ` Martin J. Bligh

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=20021203121521.GB30431@suse.de \
    --to=davej@codemonkey.org.uk \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=linux-kernel@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.