Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757799AbXHNPH7 (ORCPT ); Tue, 14 Aug 2007 11:07:59 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753232AbXHNPHt (ORCPT ); Tue, 14 Aug 2007 11:07:49 -0400 Received: from ra.tuxdriver.com ([70.61.120.52]:2580 "EHLO ra.tuxdriver.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752947AbXHNPHs (ORCPT ); Tue, 14 Aug 2007 11:07:48 -0400 Date: Tue, 14 Aug 2007 10:45:53 -0400 From: "John W. Linville" To: Adrian Bunk Cc: Arjan van de Ven , Trond Myklebust , Mariusz Kozlowski , Joe Perches , akpm@linux-foundation.org, linux-kernel@vger.kernel.org, torvalds@linux-foundation.org Subject: Re: [PATCH] [1/2many] - FInd the maintainer(s) for a patch - scripts/get_maintainer.pl Message-ID: <20070814144553.GD7198@tuxdriver.com> References: <1186984174.10249.7.camel@localhost> <200708131933.10125.m.kozlowski@tuxland.pl> <1187026955.2688.4.camel@laptopd505.fenrus.org> <1187037445.6628.98.camel@heimdal.trondhjem.org> <1187054366.2757.0.camel@laptopd505.fenrus.org> <20070814142205.GP18945@stusta.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070814142205.GP18945@stusta.de> User-Agent: Mutt/1.5.14 (2007-02-12) Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1610 Lines: 38 On Tue, Aug 14, 2007 at 04:22:05PM +0200, Adrian Bunk wrote: > On Mon, Aug 13, 2007 at 06:19:26PM -0700, Arjan van de Ven wrote: > > > > On Mon, 2007-08-13 at 16:37 -0400, Trond Myklebust wrote: > > > On Mon, 2007-08-13 at 10:42 -0700, Arjan van de Ven wrote: > > > > The maintainer info should be in the source file itself! That's the only > > > > reasonable way to keep it updated; now I'm all for having it machine > > > > parsable so that tools can use it, but it still really should be in the > > > > code itself, not in some central file that will always just go out of > > > > data, and will be a huge source of needless patch conflicts. > > > > > > If the problem is to do with people failing to update the MAINTAINERS > > > file, why would moving the same data into 20 or 30 source files motivate > > > them to keep it up to date? As far as I can see, that would just serve > > > to multiply the amount of stale data... > > > > if each .c file has a MODULE_MAINTAINER() tag... > > > > people tend to update .c files a lot better than way off-the-side other > > files. > > The move of netdev to vger would have required updating > approx. 1300 C files... Wouldn't it be individuals listed in MODULE_MAINTAINER? Even if it is the mailing list, is this the kind of thing that sed is perfect to handle? John -- John W. Linville linville@tuxdriver.com - 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/