From: "Bilbao, Carlos" <carlos.bilbao@amd.com>
To: Akira Yokosawa <akiyks@gmail.com>
Cc: "Naik, Avadhut" <Avadhut.Naik@amd.com>,
"bilbao@vt.edu" <bilbao@vt.edu>,
"corbet@lwn.net" <corbet@lwn.net>,
"elena.reshetova@intel.com" <elena.reshetova@intel.com>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"rdunlap@infradead.org" <rdunlap@infradead.org>
Subject: Re: [PATCH v2] docs/MAINTAINERS: Update my email address
Date: Tue, 23 Apr 2024 11:10:55 -0500 [thread overview]
Message-ID: <d36d68dc-a420-43c5-a633-3eb507b6c3dd@amd.com> (raw)
In-Reply-To: <b1078bb2-bea1-4b32-9b4b-4c62e02e3ef4@gmail.com>
Hello Akira,
On 4/23/2024 10:59 AM, Akira Yokosawa wrote:
> Hi Carlos,
>
> On Tue, 23 Apr 2024 10:19:14 -0500, Carlos Bilbao wrote:
>> In the near future, I will not have access to the email address I used as
>> maintainer of a number of things, mostly in the documentation. Update that
>> address to my personal email address (see Link) so I can continue
>> contributing and update .mailmap.
>>
>> Link: https://lore.kernel.org/all/BL1PR12MB58749FF2BFEDB817DE1FE6CBF82A2@BL1PR12MB5874.namprd12.prod.outlook.com/
>> Signed-off-by: Carlos Bilbao <carlos.bilbao@amd.com>
>> ---
>>
>> Changes since v1:
>> - Update .mailmap
>>
>> ---
>> .mailmap | 1 +
> [...]
>
>>
>> diff --git a/.mailmap b/.mailmap
>> index 1eb607efcc6e..4bac5578426a 100644
>> --- a/.mailmap
>> +++ b/.mailmap
>> @@ -113,6 +113,7 @@ Brian Silverman <bsilver16384@gmail.com> <brian.silverman@bluerivertech.com>
>> Cai Huoqing <cai.huoqing@linux.dev> <caihuoqing@baidu.com>
>> Can Guo <quic_cang@quicinc.com> <cang@codeaurora.org>
>> Carl Huang <quic_cjhuang@quicinc.com> <cjhuang@codeaurora.org>
>> +Carlos Bilbao <carlos.bilbao@amd.com> <carlos.bilbao.osdev@gmail.com>
>
> I'm afraid this won't do what you'd expect.
> Entries in .mailmap should look like:
>
> Full Name <new address> <old address>
>
> See gitmailmap(5) and git-check-mailmap(1) for further info.
I find it interesting that <new-email> <old-email> (as opposed to
<old-email> <new-email>) feels counterintuitive to me. Thanks for catching
this, Akira. I'm sending v3 right away.
>
> HTH, Akira
>
>
Best,
Carlos
prev parent reply other threads:[~2024-04-23 16:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-23 15:19 [PATCH v2] docs/MAINTAINERS: Update my email address Bilbao, Carlos
2024-04-23 15:59 ` Akira Yokosawa
2024-04-23 16:10 ` Bilbao, Carlos [this message]
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=d36d68dc-a420-43c5-a633-3eb507b6c3dd@amd.com \
--to=carlos.bilbao@amd.com \
--cc=Avadhut.Naik@amd.com \
--cc=akiyks@gmail.com \
--cc=bilbao@vt.edu \
--cc=corbet@lwn.net \
--cc=elena.reshetova@intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.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 read-only IMAP folder(s) and NNTP newsgroup(s).