[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1222146633.18133.51.camel@localhost>
Date: Mon, 22 Sep 2008 22:10:33 -0700
From: Joe Perches <joe@...ches.com>
To: Uwe Kleine-König <ukleinek@...len.de>
Cc: "H. Peter Anvin" <hpa@...or.com>,
Pekka Enberg <penberg@...helsinki.fi>,
Ben Dooks <ben-linux@...ff.org>,
Denis Vlasenko <vda@...t.imtp.ilyichevsk.odessa.ua>,
linux-kernel@...r.kernel.org
Subject: Re: [RFC] List of maintainers (draft #3)
On Mon, 2008-09-22 at 21:42 +0200, Uwe Kleine-König wrote:
> Continuing planning how to implement such an automation I found that
> git-send-email already has an option --cc-cmd=/path/to/some/program
I added cc-cmd to git-send-email.
> To go forward with how to specify a file <-> maintainer relation I
> suggest to standardize a field F in MAINTAINERS that specifies the
> associated files.
I did roughly the same thing last year with MAINTAINERS entries
and a script for patch submission.
http://lkml.org/lkml/2007/8/13/17
There were a few iterations before Linus said he didn't much
like the idea.
http://lkml.org/lkml/2007/8/13/1139
I still think it's useful and don't think a particularly
better way exists to generate this information.
I think the best way to manage this content is to separate
the monolithic MAINTAINERS into separate Maintainers/subsection
files (which would be automatically alphabetized) and to create
an aggregated MAINTAINERS file via Makefile.
If per directory .maintainers files are created, there'll
be roughly the same number of files.
http://lkml.org/lkml/2007/8/17/119
cheers, Joe
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists