public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Chris Snook <csnook@redhat.com>
Cc: "Robert P. J. Day" <rpjday@mindspring.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: tracking MAINTAINERS versus tracking SUBSYSTEMS
Date: Mon, 20 Aug 2007 12:46:54 -0700	[thread overview]
Message-ID: <1187639214.5963.19.camel@localhost> (raw)
In-Reply-To: <46C9EC1F.3070004@redhat.com>

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 
> netdev@vger.kernel.org, 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?

For instance:

ATL1 has this maintainer block:

        ATL1 ETHERNET DRIVER
        P: Jay Cliburn
        M: jcliburn@gmail.com
        P: Chris Snook
        M: csnook@redhat.com
        L: atl1-devel@lists.sourceforge.net
        W: http://sourceforge.net/projects/atl1
        W: http://atl1.sourceforge.net
        S: Maintained
        F: drivers/net/atl1/
        
and NETWORK DEVICE DRIVERS has:

        NETWORK DEVICE DRIVERS
        P: Andrew Morton
        M: akpm@linux-foundation.org
        P: Jeff Garzik
        M: jgarzik@pobox.com
        L: netdev@vger.kernel.org
        T: git kernel.org:/pub/scm/linux/kernel/git/jgarzik/netdev-2.6.git
        S: Maintained
        F: drivers/net/
        
So, NETWORK DEVICE DRIVERS would be CC'd on any change
to ATL1 (or any other driver in drivers/net/...)

Of course the same lookup could apply to L: or T:

cheers,  Joe



  reply	other threads:[~2007-08-20 19:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-18 17:35 tracking MAINTAINERS versus tracking SUBSYSTEMS Robert P. J. Day
2007-08-19  0:32 ` Joe Perches
2007-08-19 12:22   ` Robert P. J. Day
2007-08-19 15:37     ` Joe Perches
2007-08-19 20:10     ` Krzysztof Halasa
2007-08-20 19:31   ` Chris Snook
2007-08-20 19:46     ` Joe Perches [this message]
2007-08-21 19:22       ` Chris Snook

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1187639214.5963.19.camel@localhost \
    --to=joe@perches.com \
    --cc=csnook@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rpjday@mindspring.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox