linux-kernel - get_maintainer.pl and .mailmap entries with more than 2 addresses

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 02 Aug 2016 09:36:21 -0700
From:	Joe Perches <joe@...ches.com>
To:	Florian Mickler <florian@...kler.org>
Cc:	Mauro Carvalho Chehab <mchehab@...nel.org>,
	Shuah Khan <shuah@...nel.org>,
	LKML <linux-kernel@...r.kernel.org>, git <git@...r.kernel.org>
Subject: get_maintainer.pl and .mailmap entries with more than 2 addresses

Hello Florian.

There is at least an oddity with get_maintainer handling of a
.mailmap entry form.

For instance:

Mauro's .mailmap entry is:
Mauro Carvalho Chehab <mchehab@...nel.org> <maurochehab@...il.com> <mchehab@...radead.org> <mchehab@...hat.com> <m.chehab@...sung.com> <mchehab@....samsung.com> <mchehab@...pensource.com>

Is this a valid form?

get_maintainer output for Mauro is:

$ ./scripts/get_maintainer.pl drivers/media/ -f
Mauro Carvalho Chehab <mchehab@...nel.org> <maurochehab@...il.com> <mchehab@...radead.org> <mchehab@...hat.com> <m.chehab@...sung.com> <mchehab@....samsung.com> (maintainer:MEDIA INPUT INFRASTRUCTURE (V4L/DVB))

I believe the Mauro's and Shuah's .mailmap entries are improper and
should be changed, but I'm not completely aware of git .mailmap
handling and the documentation seems weakly specified.

https://git-scm.com/docs/git-check-mailmap

Maybe get_maintainer.pl needs a change or perhaps this patch
is  appropriate.
---
 .mailmap | 12 ++++++++++--
 1 file changed, 10 insertions(+), 2 deletions(-)

diff --git a/.mailmap b/.mailmap
index c0d5704..c7f92ca 100644
--- a/.mailmap
+++ b/.mailmap
@@ -96,7 +96,12 @@ Linus Lüssing <linus.luessing@...3.blue> <linus.luessing@....de>
 Linus Lüssing <linus.luessing@...3.blue> <linus.luessing@...om.ch>
 Mark Brown <broonie@...ena.org.uk>
 Matthieu CASTET <castet.matthieu@...e.fr>
-Mauro Carvalho Chehab <mchehab@...nel.org> <maurochehab@...il.com> <mchehab@...radead.org> <mchehab@...hat.com> <m.chehab@...sung.com> <mchehab@....samsung.com> <mchehab@...pensource.com>
+Mauro Carvalho Chehab <mchehab@...nel.org> <maurochehab@...il.com>
+Mauro Carvalho Chehab <mchehab@...nel.org> <mchehab@...radead.org>
+Mauro Carvalho Chehab <mchehab@...nel.org> <mchehab@...hat.com>
+Mauro Carvalho Chehab <mchehab@...nel.org> <m.chehab@...sung.com>
+Mauro Carvalho Chehab <mchehab@...nel.org> <mchehab@....samsung.com>
+Mauro Carvalho Chehab <mchehab@...nel.org> <mchehab@...pensource.com>
 Matt Ranostay <mranostay@...il.com> Matthew Ranostay <mranostay@...eddedalley.com>
 Matt Ranostay <mranostay@...il.com> <matt.ranostay@...el.com>
 Mayuresh Janorkar <mayur@...com>
@@ -132,7 +137,10 @@ Santosh Shilimkar <santosh.shilimkar@...cle.org>
 Sascha Hauer <s.hauer@...gutronix.de>
 S.Çağlar Onur <caglar@...dus.org.tr>
 Shiraz Hashim <shiraz.linux.kernel@...il.com> <shiraz.hashim@...com>
-Shuah Khan <shuah@...nel.org> <shuahkhan@...il.com> <shuah.khan@...com> <shuahkh@....samsung.com> <shuah.kh@...sung.com>
+Shuah Khan <shuah@...nel.org> <shuahkhan@...il.com>
+Shuah Khan <shuah@...nel.org> <shuah.khan@...com>
+Shuah Khan <shuah@...nel.org> <shuahkh@....samsung.com>
+Shuah Khan <shuah@...nel.org> <shuah.kh@...sung.com>
 Simon Kelley <simon@...kelleys.org.uk>
 Stéphane Witzmann <stephane.witzmann@...mes.univ-bpclermont.fr>
 Stephen Hemminger <shemminger@...l.org>