From: Jonathan Corbet <corbet@lwn.net>
To: Chao Yu <yuchao0@huawei.com>
Cc: <linux-doc@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<chao@kernel.org>, <jaegeuk@kernel.org>
Subject: Re: [PATCH] mailmap: add entry for Jaegeuk Kim
Date: Fri, 2 Aug 2019 07:26:26 -0600 [thread overview]
Message-ID: <20190802072626.405246e3@lwn.net> (raw)
In-Reply-To: <20190802012135.31419-1-yuchao0@huawei.com>
On Fri, 2 Aug 2019 09:21:35 +0800
Chao Yu <yuchao0@huawei.com> wrote:
> Add entry to connect all Jaegeuk's email addresses.
>
> Acked-by: Jaegeuk Kim <jaegeuk@kernel.org>
> Signed-off-by: Chao Yu <yuchao0@huawei.com>
> ---
> .mailmap | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/.mailmap b/.mailmap
> index 477debe3d960..70d41c86e644 100644
> --- a/.mailmap
> +++ b/.mailmap
> @@ -89,6 +89,9 @@ Henrik Kretzschmar <henne@nachtwindheim.de>
> Henrik Rydberg <rydberg@bitmath.org>
> Herbert Xu <herbert@gondor.apana.org.au>
> Jacob Shin <Jacob.Shin@amd.com>
> +Jaegeuk Kim <jaegeuk@kernel.org> <jaegeuk@google.com>
> +Jaegeuk Kim <jaegeuk@kernel.org> <jaegeuk@motorola.com>
> +Jaegeuk Kim <jaegeuk@kernel.org> <jaegeuk.kim@samsung.com>
So as I understand it, the mailmap file is there mostly to ensure that a
person's changesets are properly collected in 'git shortlog' and such. As
documented on the man page, it is used when a person's name is spelled
differently at different times.
That doesn't appear to be the case here, and shortlog output is correct
already. Given that, do we *really* need to maintain a collection of old
email addresses in the mailmap file? What is the benefit of that?
Thanks,
jon
next prev parent reply other threads:[~2019-08-02 13:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-02 1:21 [PATCH] mailmap: add entry for Jaegeuk Kim Chao Yu
2019-08-02 13:26 ` Jonathan Corbet [this message]
2019-08-02 14:23 ` Chao Yu
2019-08-08 14:37 ` Chao Yu
2019-08-09 16:28 ` Jonathan Corbet
2019-08-12 1:49 ` Chao Yu
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=20190802072626.405246e3@lwn.net \
--to=corbet@lwn.net \
--cc=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=yuchao0@huawei.com \
/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