From: Joe Perches <joe@perches.com>
To: Florian Mickler <florian@mickler.org>
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>,
Shuah Khan <shuah@kernel.org>,
LKML <linux-kernel@vger.kernel.org>, git <git@vger.kernel.org>,
mchehab@s-opensource.com
Subject: Re: get_maintainer.pl and .mailmap entries with more than 2 addresses
Date: Tue, 02 Aug 2016 15:26:17 -0700 [thread overview]
Message-ID: <1470176777.3998.203.camel@perches.com> (raw)
In-Reply-To: <6A56763C-D795-4943-AFE9-8A53ECD61AF6@mickler.org>
On Wed, 2016-08-03 at 00:17 +0200, Florian Mickler wrote:
> cc'd mchehab@s-opensource.com (Mauro, is your kernel.org address up?)
>
> Am Tue, 02 Aug 2016 09:36:21 -0700
> schrieb Joe Perches <joe@perches.com>:
>
> >
> > 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@kernel.org> <maurochehab@gmail.com>
> > <mchehab@infradead.org> <mchehab@redhat.com> <m.chehab@samsung.com>
> > <mchehab@osg.samsung.com> <mchehab@s-opensource.com>
> >
> > Is this a valid form?
> >
> > get_maintainer output for Mauro is:
> >
> > $ ./scripts/get_maintainer.pl drivers/media/ -f
> > Mauro Carvalho Chehab <mchehab@kernel.org> <maurochehab@gmail.com>
> > <mchehab@infradead.org> <mchehab@redhat.com> <m.chehab@samsung.com>
> > <mchehab@osg.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.
> >
> Hmm.. looking at Mauros last .mailmap commit it seems like your patch is
> ok for Mauro.
>
> Although <mywing81@gmail.com> and <mchehab@brturbo.com.br> are probably
> missing? (@Mauro)
>
>
> $ git shortlog | grep "^Mauro C"
> Mauro Carvalho Chehab (4404):
> $ git log | grep "^Author:.*Mauro Carvalho Chehab" | sort | uniq -c
> 2 Author: Mauro Carvalho Chehab <maurochehab@gmail.com>
> 146 Author: Mauro Carvalho Chehab <mchehab@brturbo.com.br>
> 645 Author: Mauro Carvalho Chehab <mchehab@infradead.org>
> 794 Author: Mauro Carvalho Chehab <mchehab@osg.samsung.com>
> 2015 Author: Mauro Carvalho Chehab <mchehab@redhat.com>
> 448 Author: Mauro Carvalho Chehab <m.chehab@samsung.com>
> 353 Author: Mauro Carvalho Chehab <mchehab@s-opensource.com>
> 1 Author: Mauro Carvalho Chehab <mywing81@gmail.com>
>
>
>
> Anyway, from a technical viewpoint your patches seem to fix
> the .mailmap entry as the author intended. (See Junio's Email for the
> documantation part)
> But I would wait for the ack from Mauro and Shuah.
As far as I understand, a single entry with just their
name and preferred email address would work too because
the name parts are all spelled identically.
next prev parent reply other threads:[~2016-08-02 22:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-02 16:36 get_maintainer.pl and .mailmap entries with more than 2 addresses Joe Perches
2016-08-02 18:16 ` Junio C Hamano
[not found] ` <6A56763C-D795-4943-AFE9-8A53ECD61AF6@mickler.org>
2016-08-02 22:26 ` Joe Perches [this message]
2016-08-02 23:11 ` Shuah Khan
2016-08-03 0:50 ` Mauro Carvalho Chehab
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=1470176777.3998.203.camel@perches.com \
--to=joe@perches.com \
--cc=florian@mickler.org \
--cc=git@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=mchehab@s-opensource.com \
--cc=shuah@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).