From: Joe Perches <joe@perches.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Rob Herring <robh@kernel.org>,
Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: [PATCH] get_maintainer: Exclude MAINTAINERS file(s) from --git-fallback and --git-blame
Date: Fri, 21 Aug 2020 10:40:15 -0700 [thread overview]
Message-ID: <1787fba7e252f053ef321b349f3bac39a8cdf503.camel@perches.com> (raw)
In-Reply-To: <CAL_JsqLBfwXamvCB0C9ujhy-BS6P4BpU-MWPuZX+_+sYPVsUSg@mail.gmail.com>
MAINTAINERS files generally have no specific maintainer but are updated
by individuals for subsystems all over the source tree.
Exclude MAINTAINERS file(s) from --git-fallback and --git-blame searches
so the unlucky individuals that update the files the most are not shown.
Signed-off-by: Joe Perches <joe@perches.com>
---
scripts/get_maintainer.pl | 1 +
1 file changed, 1 insertion(+)
diff --git a/scripts/get_maintainer.pl b/scripts/get_maintainer.pl
index 484d2fbf5921..4d5196a11329 100755
--- a/scripts/get_maintainer.pl
+++ b/scripts/get_maintainer.pl
@@ -953,6 +953,7 @@ sub get_maintainers {
}
foreach my $file (@files) {
+ next if ($file =~ /MAINTAINERS$/);
if ($email &&
($email_git || ($email_git_fallback &&
!$exact_pattern_match_hash{$file}))) {
next prev parent reply other threads:[~2020-08-21 17:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-21 15:48 [PATCH] MAINTAINERS: Add entry for HPE Superdome Flex (UV) maintainers Steve Wahl
2020-08-21 16:45 ` Rob Herring
2020-08-21 17:05 ` Joe Perches
2020-08-21 18:17 ` Rob Herring
2020-08-21 18:35 ` Joe Perches
2020-08-21 17:40 ` Joe Perches [this message]
2020-08-21 18:05 ` [PATCH V2] get_maintainer: Exclude MAINTAINERS file(s) from --git-fallback Joe Perches
2020-08-24 14:45 ` [PATCH] MAINTAINERS: Add entry for HPE Superdome Flex (UV) maintainers Steve Wahl
2020-08-24 15:36 ` Borislav Petkov
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=1787fba7e252f053ef321b349f3bac39a8cdf503.camel@perches.com \
--to=joe@perches.com \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab+huawei@kernel.org \
--cc=robh@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;
as well as URLs for NNTP newsgroup(s).