lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <875xm9tg4z.fsf@trenco.lwn.net>
Date: Mon, 20 Jan 2025 12:54:52 -0700
From: Jonathan Corbet <corbet@....net>
To: Carlos Bilbao <carlos.bilbao.osdev@...il.com>, carlos.bilbao@...nel.org
Cc: avadhut.naik@....com, akpm@...ux-foundation.org,
 linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] mailmap, docs: Update email to carlos.bilbao@...nel.org

Carlos Bilbao <carlos.bilbao.osdev@...il.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@...il.com> <carlos.bilbao@....com>

...says to map the @amd.com address to the gmail address.  But this new
line:

> Carlos Bilbao <carlos.bilbao@...nel.org> <carlos.bilbao@....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?

Thanks,

jon

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ