Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1761104AbXHPPbl (ORCPT ); Thu, 16 Aug 2007 11:31:41 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754943AbXHPPbW (ORCPT ); Thu, 16 Aug 2007 11:31:22 -0400 Received: from iolanthe.rowland.org ([192.131.102.54]:35783 "HELO iolanthe.rowland.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1763226AbXHPPbK (ORCPT ); Thu, 16 Aug 2007 11:31:10 -0400 Date: Thu, 16 Aug 2007 11:31:04 -0400 (EDT) From: Alan Stern X-X-Sender: stern@iolanthe.rowland.org To: Rene Herman cc: Kyle Moffett , Salikh Zakirov , Junio C Hamano , LKML Kernel , Joe Perches , Andrew Morton , Linus Torvalds , , Subject: Re: [linux-pm] Re: Storing Maintainers info around the kernel tree In-Reply-To: <46C469A5.8020003@gmail.com> 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: 1557 Lines: 37 On Thu, 16 Aug 2007, Rene Herman wrote: > > It would be much easier to put in the "kernel/somesubsys" directory a > > Maintainers file which has: > > It's ofcourse possible, but note that if we want this stuff to be minimally > manual, moving files around (and deleting them) then requires editing these > actual in-tree files via a tool. > > With the properties deleting files just requires deleting any file-specific > properties alongside which is trivial since those are linked from the file. > > Moving stuff works by building a list of all properties that are set on the > source starting at the source and destination's highest shared parent > directory and then reconstructing this list at the destination, striking > properties off the list that are already set at the destination. > > Adding properties, alongside added files or after the fact, could be done > via standard patch submissals via the kind of "meta-diff" that already > exists for "git move". > > I really believe this stuff should be meta-data -- and these properties as > outlined work well it seems. Please remember that not everybody uses git. The MAINTAINERS data should be available in the kernel source itself. (Maybe your suggestion is consistent with this -- I simply wanted to raise the point.) Alan Stern - 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/