From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S964991AbYEBRtS (ORCPT ); Fri, 2 May 2008 13:49:18 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1755951AbYEBRtH (ORCPT ); Fri, 2 May 2008 13:49:07 -0400 Received: from ogre.sisk.pl ([217.79.144.158]:56402 "EHLO ogre.sisk.pl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755023AbYEBRtG (ORCPT ); Fri, 2 May 2008 13:49:06 -0400 From: "Rafael J. Wysocki" To: Daniel Hazelton Subject: Re: How to reduce the number of open kernel bugs Date: Fri, 2 May 2008 19:48:47 +0200 User-Agent: KMail/1.9.6 (enterprise 20070904.708012) Cc: "Parag Warudkar" , "Adrian Bunk" , LKML References: <82e4877d0805020742l7d4a6ec9mc72e79aa3d242348@mail.gmail.com> <82e4877d0805021030s793835a1le0032673b0f4c6c7@mail.gmail.com> <200805021344.59492.dhazelton@enter.net> In-Reply-To: <200805021344.59492.dhazelton@enter.net> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200805021948.48345.rjw@sisk.pl> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Friday, 2 of May 2008, Daniel Hazelton wrote: > On Friday 02 May 2008 13:30:23 Parag Warudkar wrote: > > On Fri, May 2, 2008 at 12:29 PM, Daniel Hazelton > > wrote: This is what Adrian was pointing > > > > > ... out and is exactly what shouldn't be happening. > > > > I wasn't arguing that it is what should be happening - I was just > > pointing out that there are worse things than that routinely happen in > > distro bugzillas! > > I have to admit that this is the truth. I've seen it myself. (Hell, I won't > touch a bug-tracking system for that reason.) > > > Also I feel that if maintainer refuse to fix something - that's a dead > > end as far as that particular bug is considered. We can try and track > > such bugs in different STATUS but there would have to be people > > interested in digging through such bugs and willing to fix it after > > the maintainer has given up. Which is possible but not likely. > > > > Parag > > And I have to agree here. But there should be something that can be done > to "coax" the maintainers that pull that kind of immature crap into acting > mature and responsible. Well, how exactly would you want to do that? Rafael