From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Andrea Parri <parri.andrea@gmail.com>, Akira Yokosawa <akiyks@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org,
Alan Stern <stern@rowland.harvard.edu>,
Will Deacon <will@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Boqun Feng <boqun.feng@gmail.com>,
Nicholas Piggin <npiggin@gmail.com>,
David Howells <dhowells@redhat.com>,
Jade Alglave <j.alglave@ucl.ac.uk>,
Luc Maranget <luc.maranget@inria.fr>,
"Paul E. McKenney" <paulmck@linux.ibm.com>,
Daniel Lustig <dlustig@nvidia.com>
Subject: Re: [PATCH] MAINTAINERS: Update e-mail address for Andrea Parri
Date: Mon, 05 Aug 2019 08:23:38 -0700 [thread overview]
Message-ID: <1565018618.3341.6.camel@HansenPartnership.com> (raw)
In-Reply-To: <20190805151545.GA1615@aparri>
On Mon, 2019-08-05 at 17:15 +0200, Andrea Parri wrote:
> > Why don't you also add an entry in .mailmap as Will did in commit
> > c584b1202f2d ("MAINTAINERS: Update my email address to use
> > @kernel.org")?
>
> I considered it but could not understand its purpose... Maybe you
> can explain it to me? ;-) (can resend with this change if
> needed/desired).
man git-shortlog gives you the gory detail, but its use is to "coalesce
together commits by the same person in the shortlog, where their name
and/or email address was spelled differently." The usual way this
happens is that people have the name that appears in the From field
with and without initials.
James
next prev parent reply other threads:[~2019-08-05 15:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-05 12:15 [PATCH] MAINTAINERS: Update e-mail address for Andrea Parri Andrea Parri
2019-08-05 15:01 ` Akira Yokosawa
2019-08-05 15:15 ` Andrea Parri
2019-08-05 15:23 ` James Bottomley [this message]
2019-08-05 16:21 ` Andrea Parri
2019-08-05 17:43 ` Paul E. McKenney
2019-08-05 18:09 ` James Bottomley
2019-08-05 22:17 ` Paul E. McKenney
2019-08-07 16:01 ` Paul E. McKenney
-- strict thread matches above, loose matches on Subject: below --
2018-04-20 16:16 Andrea Parri
2018-04-20 20:30 ` 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=1565018618.3341.6.camel@HansenPartnership.com \
--to=james.bottomley@hansenpartnership.com \
--cc=akiyks@gmail.com \
--cc=boqun.feng@gmail.com \
--cc=dhowells@redhat.com \
--cc=dlustig@nvidia.com \
--cc=j.alglave@ucl.ac.uk \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luc.maranget@inria.fr \
--cc=npiggin@gmail.com \
--cc=parri.andrea@gmail.com \
--cc=paulmck@linux.ibm.com \
--cc=peterz@infradead.org \
--cc=stern@rowland.harvard.edu \
--cc=will@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.