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 15:34:46 -0500 [thread overview]
Message-ID: <20030320203446.GE1757@Master.Wizards> (raw)
In-Reply-To: <3E7A1871.4090505@us.ibm.com>
On Thu, Mar 20, 2003 at 02:37:21PM -0500, Stacy Woods wrote:
> Murray J. Root wrote:
>
> >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.
> >>
> Murray,
> Bugs 389 and 413 show the "last update" date was March 12th which
> dosen't fall
> within the two week criteria. The search is done only on the "last
> update" and
> has nothing to do with severity. Since you added comments to those
> bugs it set
> the date then. I realize this is not a perfect system to list all bugs
> that are truly
> not being worked on, but hopefully it gets some bugs investigated
> Especially the
> ones owned by bugme-janitors.
>
Thanks for the explanation - now I just need to find ways to add info to a
bug report without affecting the "last updated" time - IRC memos to gregkh?
*G*
next prev parent reply other threads:[~2003-03-20 20:24 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
2003-03-20 19:37 ` Stacy Woods
2003-03-20 20:34 ` Murray J. Root [this message]
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=20030320203446.GE1757@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 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.