public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Carlos Bilbao <carlos.bilbao.osdev@gmail.com>
To: Jonathan Corbet <corbet@lwn.net>, carlos.bilbao@kernel.org
Cc: avadhut.naik@amd.com, akpm@linux-foundation.org,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mailmap, docs: Update email to carlos.bilbao@kernel.org
Date: Sat, 25 Jan 2025 09:37:39 -0600	[thread overview]
Message-ID: <c5ecf4a3-dbd4-4ba9-ae63-66ba396cecef@gmail.com> (raw)
In-Reply-To: <875xm9tg4z.fsf@trenco.lwn.net>

Hello,

On 1/20/25 13:54, Jonathan Corbet wrote:
> Carlos Bilbao <carlos.bilbao.osdev@gmail.com> writes:
>
>> By records I meant mappings of older to newer emails, which in my head
>> is .mailmap purpose with version control. Do you think some of the
>> mappings as I've added them are redundant and/or problematic?
> My point is that this line, which is in .mailmap now (and which your
> patch preserves):
>
>> Carlos Bilbao <carlos.bilbao.osdev@gmail.com> <carlos.bilbao@amd.com>
> ...says to map the @amd.com address to the gmail address.  But this new
> line:
>
>> Carlos Bilbao <carlos.bilbao@kernel.org> <carlos.bilbao@amd.com>
> says to map @amd.com to @kernel.org instead.  At best, this is
> nonsensical; at worst, you may not get the full remapping of @amd.com
> that you seem to want.  So ... why leave that line in place?


That makes sense, thanks forclarifying. Sending out a patch correcting this
and updating myemail in MAINTAINERS now. Enjoy the weekend!
>
> Thanks,
>
> jon

Regards,
Carlos

      reply	other threads:[~2025-01-25 15:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-11 16:11 [PATCH] mailmap, docs: Update email to carlos.bilbao@kernel.org carlos.bilbao
2025-01-13 17:35 ` Jonathan Corbet
2025-01-19 16:08   ` Carlos Bilbao
2025-01-19 18:03     ` Jonathan Corbet
2025-01-19 19:40       ` Carlos Bilbao
2025-01-20 19:54         ` Jonathan Corbet
2025-01-25 15:37           ` Carlos Bilbao [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=c5ecf4a3-dbd4-4ba9-ae63-66ba396cecef@gmail.com \
    --to=carlos.bilbao.osdev@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=avadhut.naik@amd.com \
    --cc=carlos.bilbao@kernel.org \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox