Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752248AbaF2DEw (ORCPT ); Sat, 28 Jun 2014 23:04:52 -0400 Received: from mail-ve0-f169.google.com ([209.85.128.169]:38617 "EHLO mail-ve0-f169.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751309AbaF2DEu (ORCPT ); Sat, 28 Jun 2014 23:04:50 -0400 MIME-Version: 1.0 In-Reply-To: <20140628201804.215ca896@alan.etchedpixels.co.uk> References: <20140628201804.215ca896@alan.etchedpixels.co.uk> Date: Sat, 28 Jun 2014 23:04:49 -0400 Message-ID: Subject: Re: Cleanup of Kernel Bugzilla From: Nick Krause To: One Thousand Gnomes Cc: stable@vger.kernel.org, "linux-kernel@vger.kernel.org" Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Thanks that's fine , I am new to kernel work , so a list of bugs would be very helpful in my helping out with debugging. Cheers Nick On Sat, Jun 28, 2014 at 3:18 PM, One Thousand Gnomes wrote: > On Fri, 27 Jun 2014 22:45:47 -0400 > Nick Krause 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 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/