All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Snook <csnook@redhat.com>
To: Joe Perches <joe@perches.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 15:31:43 -0400	[thread overview]
Message-ID: <46C9EC1F.3070004@redhat.com> (raw)
In-Reply-To: <1187483578.4200.51.camel@localhost>

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

	-- Chris

  parent reply	other threads:[~2007-08-20 19:31 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 [this message]
2007-08-20 19:46     ` Joe Perches
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=46C9EC1F.3070004@redhat.com \
    --to=csnook@redhat.com \
    --cc=joe@perches.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.