mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Wolfram Sang <w.sang@pengutronix.de>
Cc: linux-kernel@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>,
	Grant Likely <grant.likely@secretlab.ca>,
	Anton Vorontsov <avorontsov@ru.mvista.com>
Subject: Re: [PATCH 1/3] scripts/get_maintainer.pl: Add patch/file search for keywords
Date: Mon, 19 Oct 2009 08:47:30 -0700	[thread overview]
Message-ID: <1255967250.24167.621.camel@Joe-Laptop.home> (raw)
In-Reply-To: <20091019094101.GB3414@pengutronix.de>

On Mon, 2009-10-19 at 11:41 +0200, Wolfram Sang wrote:
> > @@ -149,6 +153,8 @@ while (<MAINT>) {
> >  	    if ((-d $value)) {
> >  		$value =~ s@([^/])$@$1/@;
> >  	    }
> > +	} elsif ($type eq "K") {
> > +	    $keyword_hash{@typevalue} = $value;
> 
> It matches the way how the current implementation works, but I guess somewhen
> this @typevalue-array should be converted into a hash like
>	$types{$type} = $value;
> or similar unless I missed something.

I think you missed something.

What this is doing is saving the typevalue index of the
section where the keyword is specified.  That index is
used on the type match to add maintainers.

> Maybe the file should be read completely to save the loop.

I see if that matters.

> A bit unrelated: I noticed that lkml gets always added due to "F: *". Maybe
> this list should be skipped if there has been another mailing list found?

I think that get_maintainers is generally used by people
that aren't already sure who should get an email about 
a patch or file.  I think lkml should be cc'd in almost
every case when someone is not already sure where to
send something.

cheers, Joe


  reply	other threads:[~2009-10-19 15:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-10  6:05 [PATCH 0/3] MAINTAINERS: Add and support "K:" keyword Joe Perches
2009-10-10  6:05 ` [PATCH 1/3] scripts/get_maintainer.pl: Add patch/file search for keywords Joe Perches
2009-10-19  9:41   ` Wolfram Sang
2009-10-19 15:47     ` Joe Perches [this message]
2009-10-10  6:05 ` [PATCH 2/3] MAINTAINERS: Document new "K:" entry type Joe Perches
2009-10-12 10:14   ` Jiri Kosina
2009-10-12 11:35     ` Joe Perches
2009-10-10  6:05 ` [PATCH 3/3] MAINTAINERS: Add OPEN FIRMWARE DEVICE TREE section Joe Perches
2009-10-10  6:33   ` Grant Likely

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=1255967250.24167.621.camel@Joe-Laptop.home \
    --to=joe@perches.com \
    --cc=akpm@linux-foundation.org \
    --cc=avorontsov@ru.mvista.com \
    --cc=grant.likely@secretlab.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=w.sang@pengutronix.de \
    /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

all inboxes | Powered by JetHome®