linux-kernel - Re: tracking MAINTAINERS versus tracking SUBSYSTEMS

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <46C9EC1F.3070004@redhat.com>
Date:	Mon, 20 Aug 2007 15:31:43 -0400
From:	Chris Snook <csnook@...hat.com>
To:	Joe Perches <joe@...ches.com>
CC:	"Robert P. J. Day" <rpjday@...dspring.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: tracking MAINTAINERS versus tracking SUBSYSTEMS

Joe Perches wrote:
> On Sat, 2007-08-18 at 13:35 -0400, Robert P. J. Day wrote:
>>   $ show_subsystem drivers/bluetooth/bpa10x.c
>>   BLUETOOTH
> 
> "what's a subsystem"?
> I'm not sure there is an appropriate definition.
> If there is an appropriate definition, why
> should anyone care what subsystem a particular
> file is in?

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 
netdev@...r.kernel.org, maintained by Jeff Garzik, and has the appropriate URI 
for the netdev GIT tree.

	-- Chris
-
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/