From: Martin Kepplinger <martink@posteo.de>
To: Jeffy Chen <jeffy.chen@rock-chips.com>, linux-kernel@vger.kernel.org
Cc: akpm@linux-foundation.org, markyao0591@gmail.com,
Matt Redfearn <matt.redfearn@mips.com>,
James Hogan <jhogan@kernel.org>,
Miodrag Dinic <miodrag.dinic@mips.com>,
Stephen Boyd <sboyd@codeaurora.org>,
Aleksandar Markovic <aleksandar.markovic@mips.com>,
Sebastian Reichel <sre@kernel.org>,
Paul Burton <paul.burton@mips.com>,
Marcin Nowakowski <marcin.nowakowski@mips.com>
Subject: Re: [PATCH] mailmap: update Mark Yao's email address
Date: Fri, 29 Dec 2017 13:04:27 +0100 [thread overview]
Message-ID: <063e397e-1bfc-98ac-a38e-c85c265ff824@posteo.de> (raw)
In-Reply-To: <20171229103601.3370-1-jeffy.chen@rock-chips.com>
On 2017-12-29 11:36, Jeffy Chen wrote:
> Set current email address to replace previous employers email addresses.
>
> Signed-off-by: Jeffy Chen <jeffy.chen@rock-chips.com>
> ---
>
> .mailmap | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/.mailmap b/.mailmap
> index 1469ff0d3f4d..e18cab73e209 100644
> --- a/.mailmap
> +++ b/.mailmap
> @@ -107,6 +107,7 @@ Linus Lüssing <linus.luessing@c0d3.blue> <linus.luessing@ascom.ch>
> Maciej W. Rozycki <macro@mips.com> <macro@imgtec.com>
> Marcin Nowakowski <marcin.nowakowski@mips.com> <marcin.nowakowski@imgtec.com>
> Mark Brown <broonie@sirena.org.uk>
> +Mark Yao <markyao0591@gmail.com> <mark.yao@rock-chips.com>
> Martin Kepplinger <martink@posteo.de> <martin.kepplinger@theobroma-systems.com>
> Martin Kepplinger <martink@posteo.de> <martin.kepplinger@ginzinger.com>
> Matthieu CASTET <castet.matthieu@free.fr>
>
I don't know if "replace" is the best word here. You actually map
yourself as author to email addresses for git to use. But even if you
don't rewrite your change:
Acked-by: Martin Kepplinger <martink@posteo.de>
thanks
martin
next prev parent reply other threads:[~2017-12-29 12:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-29 10:36 Jeffy Chen
2017-12-29 12:04 ` Martin Kepplinger [this message]
2017-12-29 12:21 ` JeffyChen
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=063e397e-1bfc-98ac-a38e-c85c265ff824@posteo.de \
--to=martink@posteo.de \
--cc=akpm@linux-foundation.org \
--cc=aleksandar.markovic@mips.com \
--cc=jeffy.chen@rock-chips.com \
--cc=jhogan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcin.nowakowski@mips.com \
--cc=markyao0591@gmail.com \
--cc=matt.redfearn@mips.com \
--cc=miodrag.dinic@mips.com \
--cc=paul.burton@mips.com \
--cc=sboyd@codeaurora.org \
--cc=sre@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
all inboxes | Powered by JetHome®