From: "Murray J. Root" <murrayr@brain.org>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Bugs sitting in the NEW state for more than two weeks
Date: Thu, 20 Mar 2003 13:21:35 -0500 [thread overview]
Message-ID: <20030320182135.GD1757@Master.Wizards> (raw)
In-Reply-To: <3E79D1AD.5080803@us.ibm.com>
On Thu, Mar 20, 2003 at 09:35:25AM -0500, Stacy Woods wrote:
> There are 101 bugs sitting in the NEW state for more than 2 weeks
> that don't appear to have any activity. 48 of these bugs are owned
> by bugme-janitors which are good candidates for anyone to work on.
> Please check the bugs for before working on them to see if they are
> still available.
>
> Kernel Bug Tracker: http://bugme.osdl.org
>
>
...
>
> 387 Other Other bugme-janitors@lists.osdl.org
> poll on usb device does not return immediatly when device is unplugged
>
> 388 Other Other bugme-janitors@lists.osdl.org
> 2.5.60/ioctl on usb device returns wrong length
>
> 390 Other Other bugme-janitors@lists.osdl.org
> System hang with MySql workload
...
389 is still in "new" state but doesn't appear in list
...
>
> 410 Platform i386 mbligh@aracnet.com
> unexpected IO-APIC, please file a report at http://bugzilla.kernel.org
>
> 415 Drivers Video(DR bugme-janitors@lists.osdl.org
> aty128fb.c fails to compile (logic error)
>
> 417 File Sys ext3 akpm@digeo.com
> htree much slower than regular ext3
...
413 is still in "new" state but does not appear in list
it seems your script is sorting by more than just age.
If severity "normal" means "ignore" it should be indicated - I'll start
claiming a higher level.
--
Murray J. Root
next prev parent reply other threads:[~2003-03-20 18:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-20 14:35 Bugs sitting in the NEW state for more than two weeks Stacy Woods
2003-03-20 18:21 ` Murray J. Root [this message]
2003-03-20 19:37 ` Stacy Woods
2003-03-20 20:34 ` Murray J. Root
2003-03-20 23:56 ` Greg KH
2003-03-21 6:52 ` Matthew Dharm
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=20030320182135.GD1757@Master.Wizards \
--to=murrayr@brain.org \
--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