From: Joe Perches <joe@perches.com>
To: Mauro Carvalho Chehab <mchehab@osg.samsung.com>,
Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Linux Media Mailing List <linux-media@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Shuah Khan <shuah.kh@samsung.com>
Subject: Re: [GIT PULL for v4.8-rc1] mailcap fixup for two entries
Date: Sat, 06 Aug 2016 13:10:08 -0700 [thread overview]
Message-ID: <1470514208.28648.17.camel@perches.com> (raw)
In-Reply-To: <20160806073536.2bd92a93@recife.lan>
On Sat, 2016-08-06 at 07:35 -0300, Mauro Carvalho Chehab wrote:
> Hi Linus,
>
> Please pull from my tree for a small fixup on my entry and Shuah's entry at
> .mailcap.
>
> Basically, those entries were with a syntax that makes get_maintainer.pl to
> do the wrong thing.
>
> Thanks!
> Mauro
.mailmap
The old entries were simply improper.
git shortlog wasn't doing the right thing either.
prev parent reply other threads:[~2016-08-06 20:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-06 10:35 [GIT PULL for v4.8-rc1] mailcap fixup for two entries Mauro Carvalho Chehab
2016-08-06 20:10 ` Joe Perches [this message]
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=1470514208.28648.17.camel@perches.com \
--to=joe@perches.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@osg.samsung.com \
--cc=shuah.kh@samsung.com \
--cc=torvalds@linux-foundation.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