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  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]
Date:   Thu, 16 May 2019 09:34:28 -0700
From:   Linus Torvalds <torvalds@...ux-foundation.org>
To:     Marc Gonzalez <marc.w.gonzalez@...e.fr>
Cc:     Linus Walleij <linus.walleij@...aro.org>, arm-soc <arm@...nel.org>,
        LKML <linux-kernel@...r.kernel.org>,
        Linux ARM <linux-arm-kernel@...ts.infradead.org>
Subject: Re: [GIT PULL 1/4] ARM: SoC platform updates

On Thu, May 16, 2019 at 9:00 AM Marc Gonzalez <marc.w.gonzalez@...e.fr> wrote:
>
> Your email client did something strange by changing
>
>         linux-arm-kernel@...ts.infradead.org
> to
>         "linux-alpha@...r.kernel.org" <linux-arm-kernel@...ts.infradead.org>
>
> which is odd  ;-)

Heh. Indeed.

What seems to have happened is that somebody long ago sent an email
with a missing comma (so "linux-alpha@...r.kernel.org
<linux-arm-kernel@...ts.infradead.org>" - *intending* to send to both,
but ending up with the linux-alpha list being the "name" for the
linux-arm one).

And then I replied to that email, and it got picked up as my automatic
contact. So when I replied to linux-arm-kernel@...ts.infradead.org,
and it had no name, my automatic contacts helpfully filled in that
bogus name for that list ;)

I will fix.

I note that because *you* had added the right name for the list, this
reply didn't even try to use that bogus contact name.

                 Linus

Powered by blists - more mailing lists