From: Antony Pavlov <antonynpavlov@gmail.com>
To: nm@ti.com
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH] fixup! Update .mailmap using scripts/mailmapper
Date: Thu, 16 Oct 2014 18:52:35 +0400 [thread overview]
Message-ID: <20141016185235.a006819140c162c6871d4272@gmail.com> (raw)
In-Reply-To: <543FD6BE.2040008@ti.com>
On Thu, 16 Oct 2014 09:31:26 -0500
Nishanth Menon <nm@ti.com> wrote:
> On 10/16/2014 12:28 AM, Antony Pavlov wrote:
> > +Nishanth Menon<x0nishan@ti.com>
> Could you use Nishanth Menon <nm@ti.com> ? that has been my updated mail
> address for a few years now.
Please see this quote from git-shortlog man page:
The .mailmap feature is used to coalesce together commits by the same person in the
shortlog, where their name and/or email address was spelled differently.
...
In the simple form, each line in the file consists of the canonical real name of an
author, whitespace, and an email address used in the commit (enclosed by < and >) to
map to the name.
Also please see this git-log output:
$ git log --author="Menon" | grep ^Author: | uniq
Author: Nishanth Menon <nm@ti.com>
Author: Nishanth Menon <menon.nishanth@gmail.com>
Author: Nishanth Menon <x0nishan@ti.com>
Author: Menon, Nishanth <x0nishan@ti.com>
Author: Nishanth Menon <x0nishan@ti.com>
This string in the .mailmap file
> > +Nishanth Menon <x0nishan@ti.com>
is used only for mapping "Menon, Nishanth" -> "Nishanth Menon".
Here is git-shortlog output without this string:
$ git shortlog -n -s --author="Menon"
35 Nishanth Menon
4 Menon, Nishanth
So there is no need to add additional string containing <nm@ti.com> to the .mailmap file.
--
Best regards,
Antony Pavlov
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2014-10-16 14:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-16 5:28 Antony Pavlov
2014-10-16 14:31 ` Nishanth Menon
2014-10-16 14:52 ` Antony Pavlov [this message]
2014-10-17 9:11 ` Sascha Hauer
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=20141016185235.a006819140c162c6871d4272@gmail.com \
--to=antonynpavlov@gmail.com \
--cc=barebox@lists.infradead.org \
--cc=nm@ti.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