From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Hanna Reitz <hreitz@redhat.com>
Cc: "Kevin Wolf" <kwolf@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>,
qemu-devel@nongnu.org, qemu-block@nongnu.org,
"Max Reitz" <mreitz@redhat.com>
Subject: Re: [PATCH] MAINTAINERS: Name and email address change
Date: Tue, 10 Aug 2021 13:31:31 +0100 [thread overview]
Message-ID: <YRJxo0qC6XdOHZHU@redhat.com> (raw)
In-Reply-To: <98a4f877-2cbc-e285-3055-0a7b5a7ef901@redhat.com>
On Tue, Aug 10, 2021 at 01:46:51PM +0200, Hanna Reitz wrote:
> On 10.08.21 13:29, Philippe Mathieu-Daudé wrote:
> > On 8/10/21 11:50 AM, Hanna Reitz wrote:
> > > I have changed my name and email address. Update the MAINTAINERS file
> > > to match.
> > >
> > > Signed-off-by: Hanna Reitz <hreitz@redhat.com>
> > > ---
> > > MAINTAINERS | 8 ++++----
> > > 1 file changed, 4 insertions(+), 4 deletions(-)
> > I'd recommend you to also add an entry in .mailmap:
> >
> > -- >8 --
> > diff --git a/.mailmap b/.mailmap
> > index 082ff893ab3..504839c84d3 100644
> > --- a/.mailmap
> > +++ b/.mailmap
> > @@ -53,6 +53,7 @@ Anthony Liguori <anthony@codemonkey.ws> Anthony
> > Liguori <aliguori@us.ibm.com>
> > Filip Bozuta <filip.bozuta@syrmia.com> <filip.bozuta@rt-rk.com.com>
> > Frederic Konrad <konrad@adacore.com> <fred.konrad@greensocs.com>
> > Greg Kurz <groug@kaod.org> <gkurz@linux.vnet.ibm.com>
> > +Hanna Reitz <hreitz@redhat.com> <mreitz@redhat.com>
> > Huacai Chen <chenhuacai@kernel.org> <chenhc@lemote.com>
> > Huacai Chen <chenhuacai@kernel.org> <chenhuacai@loongson.cn>
> > James Hogan <jhogan@kernel.org> <james.hogan@imgtec.com>
> > ---
>
> Hu, I didn’t know there is such a thing. Looks like I could even do
>
> Hanna Reitz <hreitz@redhat.com> Max Reitz <mreitz@redhat.com>
With the line Philippe suggested, the rewrite will happen any time
the original email is seen. With this line, the rewrite will only
happen if both original name + email match. In practice this is
functionally the same, unless someone had variations in the spelling
of their real name over time, so either would work.
> Feels a bit like cheating, though...?
I wouldn't call it cheating. It is just an input for canonicalizing
contributors' identities, where there were changes in name or email
over time. It gives a more useful view to tools like 'git shortlog'
and 'git-dm' stats reports, such that all work over time will be
grouped together instead of split.
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2021-08-10 12:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-10 9:50 [PATCH] MAINTAINERS: Name and email address change Hanna Reitz
2021-08-10 11:29 ` Philippe Mathieu-Daudé
2021-08-10 11:46 ` Hanna Reitz
2021-08-10 12:18 ` Philippe Mathieu-Daudé
2021-08-10 13:59 ` Hanna Reitz
2021-08-10 12:31 ` Daniel P. Berrangé [this message]
2021-08-10 14:00 ` Hanna Reitz
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=YRJxo0qC6XdOHZHU@redhat.com \
--to=berrange@redhat.com \
--cc=hreitz@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=philmd@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).