From: Jonathan Corbet <corbet@lwn.net>
To: Chao Yu <chao@kernel.org>
Cc: Chao Yu <yuchao0@huawei.com>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
jaegeuk@kernel.org
Subject: Re: [PATCH] mailmap: add entry for Jaegeuk Kim
Date: Fri, 9 Aug 2019 10:28:16 -0600 [thread overview]
Message-ID: <20190809102816.52b3b310@lwn.net> (raw)
In-Reply-To: <fd14e8d4-7468-ed3a-a679-6167eac72626@kernel.org>
On Thu, 8 Aug 2019 22:37:41 +0800
Chao Yu <chao@kernel.org> wrote:
> > IMO, when we use git-blame to find out who is response for specified code, w/o
> > mailmap we may just found old obsolete email address in the related commit; even
> > we can search full name for his/her new email address, how can we make sure they
> > are the same person... so anyway, it can help to find last valid/canonical email
> > address of someone.
>
> Any thoughts?
I'm not fully convinced that we want to maintain a database of every
developer's email history. But I did merge this patch a few days ago.
Thanks,
jon
next prev parent reply other threads:[~2019-08-09 16: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
2019-08-02 14:23 ` Chao Yu
2019-08-08 14:37 ` Chao Yu
2019-08-09 16:28 ` Jonathan Corbet [this message]
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=20190809102816.52b3b310@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