![]() | |||||||||||
Messages in this thread |
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@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ | ||||||||||
| Last update: 2008-09-23 07:15 [from the cache] ©2003-2008 | |||||||||||