From: Lukas Bulwahn <lukas.bulwahn@gmail.com>
To: Dwaipayan Ray <dwaipayanray1@gmail.com>
Cc: Joe Perches <joe@perches.com>,
linux-kernel-mentees@lists.linuxfoundation.org
Subject: Re: [Linux-kernel-mentees] checkpatch.pl improvement: NO_AUTHOR_SIGN_OFF warnings for users with multiple emails
Date: Mon, 21 Sep 2020 15:27:22 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.21.2009211523310.19489@felia> (raw)
In-Reply-To: <9ab72752c9c11bebc15a4a0776d1b1171cdb63bc.camel@perches.com>
On Mon, 21 Sep 2020, Joe Perches wrote:
> On Mon, 2020-09-21 at 17:41 +0530, Dwaipayan Ray wrote:
> > One possible solution is while parsing the author, also load mailmap
> > and load associated email addresses to the author and load it
> > into a hash. Next when a signed-off-by line is encountered and
> > the email is found in our hash ( or maybe some other ds ), then
> > the signed-off-by match should be positive.
> >
> > Is this feasible? I would be looking at other possibilities too. But it
> > would be great to have your view on it!
>
> Either copy the mailmap handling out of get_maintainer
> or strip it from get_maintainer and put it into a
> separate perl module/file.
>
>
Agree. Dwaipayan, I pointed you to read_mailmap here already:
https://lore.kernel.org/linux-kernel-mentees/alpine.DEB.2.21.2009181238230.14717@felia/
Lukas
_______________________________________________
Linux-kernel-mentees mailing list
Linux-kernel-mentees@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/linux-kernel-mentees
next prev parent reply other threads:[~2020-09-21 13:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-21 12:11 [Linux-kernel-mentees] checkpatch.pl improvement: NO_AUTHOR_SIGN_OFF warnings for users with multiple emails Dwaipayan Ray
2020-09-21 12:24 ` Joe Perches
2020-09-21 13:27 ` Lukas Bulwahn [this message]
2020-09-21 13:23 ` Lukas Bulwahn
2020-09-21 14:00 ` Dwaipayan Ray
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=alpine.DEB.2.21.2009211523310.19489@felia \
--to=lukas.bulwahn@gmail.com \
--cc=dwaipayanray1@gmail.com \
--cc=joe@perches.com \
--cc=linux-kernel-mentees@lists.linuxfoundation.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).