linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Wolfram Sang <w.sang@pengutronix.de>
To: Joe Perches <joe@perches.com>
Cc: linuxppc-dev@ozlabs.org, devicetree-discuss@ozlabs.org,
	linux-kernel@vger.kernel.org
Subject: Re: [RFC] scripts/get_maintainer: add emails based on keywords in the patch
Date: Sat, 10 Oct 2009 11:03:02 +0200	[thread overview]
Message-ID: <20091010090302.GA11576@pengutronix.de> (raw)
In-Reply-To: <1255114905.16347.137.camel@Joe-Laptop.home>

[-- Attachment #1: Type: text/plain, Size: 879 bytes --]


> Perhaps it's better to use the existing MAINTAINERS file
> and extend it with a new "K:" for keyword entry.

Yeah, makes sense to have everything in one file.

> +	K: Keyword perl regex pattern to match content in patch
> +	   All patterns are surrounded by "\b"
> +	   for instance: K: of_get_profile
> +	   will match patches that contain the word "of_get_profile"

...in the lines which are changed?

> +OPEN FIRMWARE DEVICE TREE
> +L:	devicetree-discuss@lists.ozlabs.org
> +S:	Odd Fixes

Maintained, I'd say. Especially as Grant Likely recently said he wants to take care about OF.

> +K:	of_get_property

F: drivers/of/

Will check the script later this weekend.

Thanks,

   Wolfram

-- 
Pengutronix e.K.                           | Wolfram Sang                |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

  reply	other threads:[~2009-10-10  9:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-09 10:32 [RFC] scripts/get_maintainer: add emails based on keywords in the patch Wolfram Sang
2009-10-09 11:23 ` Joe Perches
2009-10-09 19:01   ` Joe Perches
2009-10-10  9:03     ` Wolfram Sang [this message]
2009-10-09 15:46 ` 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=20091010090302.GA11576@pengutronix.de \
    --to=w.sang@pengutronix.de \
    --cc=devicetree-discuss@ozlabs.org \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    /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;
as well as URLs for NNTP newsgroup(s).