From: Jacob Keller <jacob.e.keller@intel.com>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: Kernel.org Tools <tools@kernel.org>
Subject: Re: [PATCH v3] b4: support send-email aliases
Date: Thu, 9 Oct 2025 15:47:45 -0700 [thread overview]
Message-ID: <85fed1e8-0028-4ada-a450-fa022eb652af@intel.com> (raw)
In-Reply-To: <20251009-space-porcupine-of-lightning-1086aa@lemur>
[-- Attachment #1.1: Type: text/plain, Size: 1177 bytes --]
On 10/9/2025 1:21 PM, Konstantin Ryabitsev wrote:
> On Thu, Oct 09, 2025 at 12:49:07PM -0700, Jacob Keller wrote:
>>> This has the following benefits:
>>>
>>> 1. If the same alias is used in 20 patches, we're only looking it up once.
>>> 2. It'll be automatically used in the following block of code without needing
>>> to modify the addresses list here.
>>>
>>
>> One other issue is that this means if you have an alias, it will not be
>> covered by mailmap.
>>
>> I'm wondering if what we want is a separate ALIAS_INFO instead?
>
> Ah, hm, you're right.
>
> Yes, go ahead and make a new global caching map. It's very unlikely to be
> more than a few entries large, so the impact should be minimal.
>
Right. It should only ever really be the number of aliases + potentially
any unintentional unqualified addresses that aren't proper aliases. Its
not even the size of every alias in your aliases file since we only load
ones which get matched.
> Then we do want to run through the list twice:
> 1. first run replacing aliases (new loop)
> 2. second run checking against mailmap (existing loop)
>
> -K
Yep, that's what I did in v4.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]
next prev parent reply other threads:[~2025-10-09 22:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-09 17:01 [PATCH v3] b4: support send-email aliases Jacob Keller
2025-10-09 18:24 ` Konstantin Ryabitsev
2025-10-09 19:01 ` Jacob Keller
2025-10-09 19:49 ` Jacob Keller
2025-10-09 20:21 ` Konstantin Ryabitsev
2025-10-09 22:47 ` Jacob Keller [this message]
2025-10-09 22:47 ` Jacob Keller
2025-10-09 20:22 ` Jacob Keller
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=85fed1e8-0028-4ada-a450-fa022eb652af@intel.com \
--to=jacob.e.keller@intel.com \
--cc=konstantin@linuxfoundation.org \
--cc=tools@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;
as well as URLs for NNTP newsgroup(s).