From: Tom Rini <trini@konsulko.com>
To: Trevor Woerner <twoerner@gmail.com>
Cc: U-Boot Mailing List <u-boot@lists.denx.de>
Subject: Re: [PATCH] scripts/get_maintainer.pl: obey ignore list
Date: Fri, 11 Jun 2021 10:23:01 -0400 [thread overview]
Message-ID: <20210611142301.GW9516@bill-the-cat> (raw)
In-Reply-To: <20210611033727.882-1-twoerner@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1257 bytes --]
On Thu, Jun 10, 2021 at 11:37:27PM -0400, Trevor Woerner wrote:
> If the user creates a .get_maintainer.ignore file, make sure it is consulted
> and obeyed for *all* emails discovered by the script.
>
> Signed-off-by: Trevor Woerner <twoerner@gmail.com>
> ---
> scripts/get_maintainer.pl | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/scripts/get_maintainer.pl b/scripts/get_maintainer.pl
> index e3b41616c9..8c0fb8656e 100755
> --- a/scripts/get_maintainer.pl
> +++ b/scripts/get_maintainer.pl
> @@ -2435,6 +2435,7 @@ sub merge_email {
>
> for (@_) {
> my ($address, $role) = @$_;
> + next if (ignore_email_address($address));
> if (!$saw{$address}) {
> if ($output_roles) {
> push(@lines, "$address ($role)");
This got me to check and see that yes, our copy of get_maintainers.pl is
out of date from Linux. And in fact, a re-sync will let us add a
.get_maintainer.conf file and use upstream a lot more closely as it now
has logic to find all MAINTAINERS files in a tree.
But this change isn't upstream. Please work with Joe Perches upstream
to get this change accepted and it'll flow down to us and not get
overwritten when I forget it was an intentional change :) Thanks!
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2021-06-11 14:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-11 3:37 [PATCH] scripts/get_maintainer.pl: obey ignore list Trevor Woerner
2021-06-11 14:23 ` Tom Rini [this message]
2021-06-11 14:56 ` Trevor Woerner
2021-06-11 21:06 ` Tom Rini
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=20210611142301.GW9516@bill-the-cat \
--to=trini@konsulko.com \
--cc=twoerner@gmail.com \
--cc=u-boot@lists.denx.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