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: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87zfj965bh.fsf@trenco.lwn.net>
Date: Wed, 29 Jan 2025 07:52:02 -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: Update incorrect entry and my email in
 MAINTAINERS

Carlos Bilbao <carlos.bilbao.osdev@...il.com> writes:

> Hello,
>
> On 1/28/25 16:05, Jonathan Corbet wrote:
>> carlos.bilbao@...nel.org writes:
>>
>>> From: Carlos Bilbao <carlos.bilbao@...nel.org>
>>>
>>> Update .mailmap to fix a mapping and my email address in MAINTAINERS.
>>>
>>> Signed-off-by: Carlos Bilbao <carlos.bilbao@...nel.org>
>>> ---
>>>  .mailmap    |  1 -
>>>  MAINTAINERS | 10 +++++-----
>>>  2 files changed, 5 insertions(+), 6 deletions(-)
>>>
>>> diff --git a/.mailmap b/.mailmap
>>> index 83837191affb..0768824e9d19 100644
>>> --- a/.mailmap
>>> +++ b/.mailmap
>>> @@ -139,7 +139,6 @@ Bryan Tan <bryan-bt.tan@...adcom.com> <bryantan@...are.com>
>>>  Cai Huoqing <cai.huoqing@...ux.dev> <caihuoqing@...du.com>
>>>  Can Guo <quic_cang@...cinc.com> <cang@...eaurora.org>
>>>  Carl Huang <quic_cjhuang@...cinc.com> <cjhuang@...eaurora.org>
>>> -Carlos Bilbao <carlos.bilbao.osdev@...il.com> <carlos.bilbao@....com>
>>>  Carlos Bilbao <carlos.bilbao@...nel.org> <carlos.bilbao.osdev@...il.com>
>>>  Carlos Bilbao <carlos.bilbao@...nel.org> <carlos.bilbao@....com>
>>>  Carlos Bilbao <carlos.bilbao@...nel.org> <bilbao@...edu>
>> So I am getting confused ... why not just send me a correct patch for
>> this file rather than expecting me to apply the incorrect one followed
>> by the fix?
>
>
> Because the incorrect one already made it upstream AFAIU:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20250128&id=ed7c0f5395e05057ae6459fdcfe229fb9aaab5b6

Hmm... it looks like Andrew took it?  It's still in linux-next, though,
and could be pulled out.  It really seems better to just do it right
from the outset?

jon

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ