Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Wed, 19 Dec 2001 05:02:11 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Wed, 19 Dec 2001 05:02:01 -0500 Received: from [213.236.192.200] ([213.236.192.200]:62994 "EHLO mail.circlestorm.org") by vger.kernel.org with ESMTP id ; Wed, 19 Dec 2001 05:01:47 -0500 Message-ID: <003301c18873$7d06f8b0$6c2876d9@dead2> From: "Dead2" Cc: In-Reply-To: <026701c187d5$ec2472c0$67c0ecd5@dead2> <20011218123724.A32316@asooo.flowerfire.com> <01121909274103.01840@manta> Subject: Re: The direction linux is taking Date: Wed, 19 Dec 2001 10:56:53 +0100 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 To: unlisted-recipients:; (no To-header on input)@localhost.localdomain Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org > What might take out a few birds with one stone is to have someone on > > lkml become an "LKML MAINTAINER": collect patches and bug reports in a > > central place. This would include: > > > > 1) The patch and/or bug report > > 2) The entire LKML thread, with "important" messages marked > > 3) Personal input, prioritization, severity info, etc. > > Good idea but _who_ will do that? Just a thought that popped into my head.. What about using some kind of BugTrack system for this? Where people can report a bug, and file patches for them. There would indeed be some situations where 2-3-4 maybe more patches are filed to fix one bug. Then the maintainer can easily look through the patches and descide what to use.. -=Dead2=- - 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/