From: "Paul E. McKenney" <paulmck@linux.ibm.com>
To: Akira Yokosawa <akiyks@gmail.com>
Cc: perfbook@vger.kernel.org
Subject: Re: [PATCH] Create .mailmap to fix unreachable email address
Date: Tue, 6 Aug 2019 09:25:44 -0700 [thread overview]
Message-ID: <20190806162544.GP28441@linux.ibm.com> (raw)
In-Reply-To: <154feeee-a7b3-17bd-6b26-6ff1778e8b42@gmail.com>
On Wed, Aug 07, 2019 at 12:45:34AM +0900, Akira Yokosawa wrote:
> >From 327971006462cbab7b5007717d7536b0e3947eb4 Mon Sep 17 00:00:00 2001
> From: Akira Yokosawa <akiyks@gmail.com>
> Date: Wed, 7 Aug 2019 00:15:12 +0900
> Subject: [PATCH] Create .mailmap to fix unreachable email address
>
> There are some commits with typo in my gmail address.
> Although they can not be fixed after the fact, "git shortlog -se"
> and "git show --use-mailmap" respect entries in .mailmap.
>
> Signed-off-by: Akira Yokosawa <akiyks@gmail.com>
Good point, queued and pushed, thank you!
While in the area, I added commit to allow for my recent email address
change and some early git misconfiguration. ;-)
Thanx, Paul
> ---
> Hi Paul,
>
> Inspired by discussion in another thread, I looked up the usage of
> .mailmap in Git repository. It can be used to partially rescue typos
> in email configs such as those made in the early days of my contributions.
>
> This will prevent the unreachable address from being displayed by
> "git shortlog -se" and the like.
>
> Thanks, Akira
> --
> .mailmap | 1 +
> 1 file changed, 1 insertion(+)
> create mode 100644 .mailmap
>
> diff --git a/.mailmap b/.mailmap
> new file mode 100644
> index 00000000..c5d1cd3e
> --- /dev/null
> +++ b/.mailmap
> @@ -0,0 +1 @@
> +<akiyks@gmail.com> <akiysw@gmail.com>
> --
> 2.17.1
>
next prev parent reply other threads:[~2019-08-06 16:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-06 15:45 [PATCH] Create .mailmap to fix unreachable email address Akira Yokosawa
2019-08-06 16:25 ` Paul E. McKenney [this message]
2019-08-06 22:21 ` Akira Yokosawa
2019-08-07 0:31 ` Paul E. McKenney
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=20190806162544.GP28441@linux.ibm.com \
--to=paulmck@linux.ibm.com \
--cc=akiyks@gmail.com \
--cc=perfbook@vger.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