From: Jani Nikula <jani.nikula@intel.com>
To: linux-kernel@vger.kernel.org, Joe Perches <joe@perches.com>
Cc: jani.nikula@intel.com
Subject: [PATCH] get_maintainer: add support for using an alternate MAINTAINERS file
Date: Fri, 16 Oct 2015 11:36:45 +0300 [thread overview]
Message-ID: <1444984605-7445-1-git-send-email-jani.nikula@intel.com> (raw)
There are large and/or complex subsystems/drivers that have domain
experts that should review patches in their domain. One such example is
drm/i915. We'd like to be able to document this in a way that can be
automatically queried for each patch, so people know who to ping for
reviews. This is what get_maintainer.pl already solves.
However, documenting all of this in the main kernel MAINTAINERS file is
just too much noise, and potentially confusing for community
contributors. Add support for specifying and using an alternate
MAINTAINERS file with --maintainers option.
Signed-off-by: Jani Nikula <jani.nikula@intel.com>
---
Note that I don't know perl, at all. This is all cargo culted copy
paste, but seems to work. Please be gentle. :)
---
scripts/get_maintainer.pl | 7 +++++--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/scripts/get_maintainer.pl b/scripts/get_maintainer.pl
index 98bae869f6d0..0dae244f26eb 100755
--- a/scripts/get_maintainer.pl
+++ b/scripts/get_maintainer.pl
@@ -18,6 +18,7 @@ my $V = '0.26';
use Getopt::Long qw(:config no_auto_abbrev);
my $lk_path = "./";
+my $maintainers_path = "${lk_path}MAINTAINERS";
my $email = 1;
my $email_usename = 1;
my $email_maintainer = 1;
@@ -229,6 +230,7 @@ if (!GetOptions(
'n!' => \$email_usename,
'l!' => \$email_list,
's!' => \$email_subscriber_list,
+ 'maintainers=s' => \$maintainers_path,
'multiline!' => \$output_multiline,
'roles!' => \$output_roles,
'rolestats!' => \$output_rolestats,
@@ -300,8 +302,8 @@ if (!top_of_kernel_tree($lk_path)) {
my @typevalue = ();
my %keyword_hash;
-open (my $maint, '<', "${lk_path}MAINTAINERS")
- or die "$P: Can't open MAINTAINERS: $!\n";
+open (my $maint, '<', $maintainers_path)
+ or die "$P: Can't open ${maintainers_path}: $!\n";
while (<$maint>) {
my $line = $_;
@@ -808,6 +810,7 @@ Other options:
--keywords => scan patch for keywords (default: $keywords)
--sections => print all of the subsystem sections with pattern matches
--mailmap => use .mailmap file (default: $email_use_mailmap)
+ --maintainers => specify alternate MAINTAINERS file to use
--version => show version
--help => show this help information
--
2.1.4
next reply other threads:[~2015-10-16 8:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-16 8:36 Jani Nikula [this message]
2015-10-16 8:50 ` Joe Perches
2015-10-16 9:14 ` Jani Nikula
2015-10-16 16:23 ` Joe Perches
2015-10-16 17:37 ` Joe Perches
2015-10-16 18:35 ` Jani Nikula
2015-10-16 18:41 ` Joe Perches
2015-10-16 18:56 ` Jani Nikula
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=1444984605-7445-1-git-send-email-jani.nikula@intel.com \
--to=jani.nikula@intel.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.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
Powered by JetHome