Joe Perches wrote:
On Mon, 2007-08-20 at 15:31 -0400, Chris Snook wrote:
Until I can pass a patch or source file as an argument to a script and get out
the URL of the git tree it needs to go into on the path to Linus's tree,
MAINTAINERS is inadequate. If I ask for the MAINTAINER info of
drivers/net/atl1/atl1_main.c, I should get back myself, my co-maintainer, our
sourceforge URL, our mailing list address, etc. There should also be a
mechanism, either as part of MAINTAINERS or something else, that will tell me
that atl1 is part of the netdev subsystem, which is discussed on
[email protected], maintained by Jeff Garzik, and has the appropriate URI
for the netdev GIT tree.
Finding a specific "List" or "Web" or "Tree" from a file is
a pretty easy extension to the current get_maintainer script.
The git_maintainer script could easily be modified to take
a filename rather than a patch file as input too.
There is no specific "parent" information in MAINTAINERS.
Are you suggesting there should be?
Still, it's easy to use directory parentage.
Is that good enough?
I suppose. I was thinking initially that directory parentage alone
wouldn't suffice, because you could be traversing upwards from a variety
of places with a complex patch. But now that I think about it, a patch
should really only be going in through one git tree, no matter how many
subsystems it might peripherally touch. Deciding which tree really
requires human intelligence, so there's no point trying to automate
that. Multiple inheritance would be... bad...
-- Chris
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
