From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753987AbbJPIhG (ORCPT ); Fri, 16 Oct 2015 04:37:06 -0400 Received: from mga14.intel.com ([192.55.52.115]:21478 "EHLO mga14.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753925AbbJPIhD (ORCPT ); Fri, 16 Oct 2015 04:37:03 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.17,688,1437462000"; d="scan'208";a="828355516" From: Jani Nikula To: linux-kernel@vger.kernel.org, Joe Perches 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 Message-Id: <1444984605-7445-1-git-send-email-jani.nikula@intel.com> X-Mailer: git-send-email 2.1.4 Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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 --- 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