public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@digeo.com>
To: linux-kernel@vger.kernel.org
Subject: kernel bugzilla
Date: Mon, 12 May 2003 16:04:46 -0700	[thread overview]
Message-ID: <20030512160446.0f717e8e.akpm@digeo.com> (raw)


We probably have a lot of bugs which just got quietly fixed, but are still
open.

Could anyone who has ever raised a bug please review the bugs which you
raised and, if necessary, retest?

If the bug is unreproducible or was just some random oops which happened
ages ago then it's probably best to close it off - it it's real then it'll
happen again.

	http://bugzilla.kernel.org/

thanks.

             reply	other threads:[~2003-05-12 22:56 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-12 23:04 Andrew Morton [this message]
2003-05-13 21:55 ` kernel bugzilla Diego Calleja García
     [not found] <20050617001330.294950ac.akpm@osdl.org>
     [not found] ` <1119016223.5049.3.camel@mulgrave>
     [not found]   ` <20050617142225.GO6957@suse.de>
2005-06-17 21:10     ` Andrew Morton
2005-06-17 21:23       ` Jens Axboe
2005-06-17 21:39         ` Andrew Morton
2005-06-18 14:50           ` Alexey Dobriyan
2005-06-18 18:23             ` Andrew Morton
2005-06-20 18:59               ` Alexey Dobriyan
2005-06-18 15:45           ` Adrian Bunk
2005-06-18 15:58             ` Martin J. Bligh
2005-06-17 21:45         ` Martin J. Bligh
2005-06-18 19:13           ` Dave Jones
2005-06-19  2:54             ` Kyle Moffett
2005-06-19  8:22               ` Dave Jones
2005-06-19 16:58                 ` Kyle Moffett
2005-06-20 11:58             ` Takashi Iwai
2005-06-20 14:08               ` Martin J. Bligh
2005-06-18  1:14         ` Herbert Xu
  -- strict thread matches above, loose matches on Subject: below --
2005-06-19 19:02 Kenneth Parrish

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=20030512160446.0f717e8e.akpm@digeo.com \
    --to=akpm@digeo.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox