Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Thu, 17 Oct 2002 20:00:27 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Thu, 17 Oct 2002 20:00:27 -0400 Received: from modemcable061.219-201-24.mtl.mc.videotron.ca ([24.201.219.61]:42131 "EHLO montezuma.mastecende.com") by vger.kernel.org with ESMTP id ; Thu, 17 Oct 2002 20:00:25 -0400 Date: Thu, 17 Oct 2002 19:52:17 -0400 (EDT) From: Zwane Mwaikambo X-X-Sender: zwane@montezuma.mastecende.com To: "Martin J. Bligh" cc: Greg KH , linux-kernel Subject: Re: Bug tracking in the run up from 2.5 to 2.6 In-Reply-To: <2261838972.1034873270@[10.10.2.3]> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 671 Lines: 20 On Thu, 17 Oct 2002, Martin J. Bligh wrote: > > If there are people to do the categorizing and "cleaning" of the > > reported bugs, I would love to use this. By "cleaning" I mean the > > following at the minimum: > > - marking bugs as duplicates of existing bugs > > - throwing away useless bug reports Sounds great, how do we handle duplicate work? ie will there be bug assignments ? Zwane -- function.linuxpower.ca - 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/