From: One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>
To: Nick Krause <xerofoify@gmail.com>
Cc: stable@vger.kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Cleanup of Kernel Bugzilla
Date: Sat, 28 Jun 2014 20:18:04 +0100 [thread overview]
Message-ID: <20140628201804.215ca896@alan.etchedpixels.co.uk> (raw)
In-Reply-To: <CAPDOMVjnROuS4D4E2B7=PxOZUB4YXHuFUKy5C9Y8Lm7gxN=N_Q@mail.gmail.com>
On Fri, 27 Jun 2014 22:45:47 -0400
Nick Krause <xerofoify@gmail.com> wrote:
> Do any of you use the kernel Bugzilla? If you do I was wondering if we
> can clean it up.
Developers are generally focussed on fixing bugs. Also the way bugzilla
works a lot of developers don't close the bugs and the originators never
get around to it.
Now if you want to clean up bugzilla then what would be really useful
(and probably quite tedious) is a list of all the bugs which end either in
- confirmation it is fixed, but the bug is not closed
- confirmation that it cannot be reproduced, but the bug is not closed
- with a question asking for more information which has had no reply in
say 3 months
Given lists of bugs in those categories I can then go and zap them.
Alan
next prev parent reply other threads:[~2014-06-28 19:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-27 18:11 Cleanup of Kernel Bugzilla Nick Krause
2014-06-28 2:45 ` Nick Krause
2014-06-28 16:06 ` Nick Krause
2014-06-28 16:55 ` Theodore Ts'o
2014-06-28 16:36 ` Theodore Ts'o
2014-06-28 19:18 ` One Thousand Gnomes [this message]
2014-06-29 3:04 ` Nick Krause
2014-06-29 6:33 ` Gideon D'souza
2014-06-29 7:21 ` Levente Kurusa
2014-06-29 21:32 ` Theodore Ts'o
2014-06-30 2:09 ` Nick Krause
2014-06-30 12:42 ` Theodore Ts'o
-- strict thread matches above, loose matches on Subject: below --
2014-06-27 2:44 Nick Krause
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=20140628201804.215ca896@alan.etchedpixels.co.uk \
--to=gnomes@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=xerofoify@gmail.com \
/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