From: Jean-Michel Hautbois <jeanmichel.hautbois@yoseli.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, axboe@kernel.dk,
stephen@networkplumber.org, o.rempel@pengutronix.de,
quic_bjorande@quicinc.com, heiko@sntech.de,
konrad.dybcio@linaro.org, kuba@kernel.org
Subject: Re: [PATCH] mailmap: add entry for Jean-Michel Hautbois
Date: Wed, 6 Mar 2024 23:00:27 +0100 [thread overview]
Message-ID: <7360e276-653f-4223-9ffd-3f701844a84f@yoseli.org> (raw)
In-Reply-To: <20240306125003.de7b09d64e28a7685eb22f17@linux-foundation.org>
Hello Andrew,
On 06/03/2024 21:50, Andrew Morton wrote:
> On Wed, 6 Mar 2024 09:59:34 +0100 Jean-Michel Hautbois <jeanmichel.hautbois@yoseli.org> wrote:
>
>> Despite having contributed several patches, my email address was not
>> previously included. This update ensures that my contributions are
>> correctly attributed.
>>
>> Signed-off-by: Jean-Michel Hautbois <jeanmichel.hautbois@yoseli.org>
>> +++ b/.mailmap
>> @@ -250,6 +250,7 @@ Jayachandran C <c.jayachandran@gmail.com> <jchandra@broadcom.com>
>> Jayachandran C <c.jayachandran@gmail.com> <jchandra@digeo.com>
>> Jayachandran C <c.jayachandran@gmail.com> <jnair@caviumnetworks.com>
>> <jean-philippe@linaro.org> <jean-philippe.brucker@arm.com>
>> +Jean-Michel Hautbois <jeanmichel.hautbois@yoseli.org>
>> Jean Tourrilhes <jt@hpl.hp.com>
>> Jeevan Shriram <quic_jshriram@quicinc.com> <jshriram@codeaurora.org>
>> Jeff Garzik <jgarzik@pretzel.yyz.us>
>> --
>
> Well, this isn't ./CREDITS. Why do we need this?
>
> .mailmap has:
>
> #
> # This list is used by git-shortlog to fix a few botched name translations
> # in the git archive, either because the author's full name was messed up
> # and/or not always written the same way, making contributions from the
> # same person appearing not to be so or badly displayed. Also allows for
> # old email addresses to map to new email addresses.
> #
>
> Now if this entry was mapping your ideasonboard.com and/or veo-labs.com
> and/or vodalys.com and/or gmail.com addresses onto one address then I
> can see why we'd need the change.
>
Indeed, I am sorry for the confusion :-/.
I will send a revised one to map the old addresses to this new one. Thanks.
JM
next prev parent reply other threads:[~2024-03-06 22:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-06 8:59 Jean-Michel Hautbois
2024-03-06 20:50 ` Andrew Morton
2024-03-06 22:00 ` Jean-Michel Hautbois [this message]
2024-06-08 13:33 Jean-Michel Hautbois
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=7360e276-653f-4223-9ffd-3f701844a84f@yoseli.org \
--to=jeanmichel.hautbois@yoseli.org \
--cc=akpm@linux-foundation.org \
--cc=axboe@kernel.dk \
--cc=heiko@sntech.de \
--cc=konrad.dybcio@linaro.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
--cc=quic_bjorande@quicinc.com \
--cc=stephen@networkplumber.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
all inboxes | Powered by JetHome®