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] [day] [month] [year] [list]
Date:   Sat, 9 Jan 2021 11:00:01 -0800
From:   Linus Torvalds <torvalds@...ux-foundation.org>
To:     "Darrick J. Wong" <darrick.wong@...cle.com>
Cc:     xfs <linux-xfs@...r.kernel.org>,
        linux-fsdevel <linux-fsdevel@...r.kernel.org>,
        Christoph Hellwig <hch@...radead.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] maintainers: update my email address

On Fri, Jan 8, 2021 at 10:46 PM Darrick J. Wong <darrick.wong@...cle.com> wrote:
>
> Change my email contact ahead of a likely painful eleven-month migration
> to a certain cobalt enteprisey groupware cloud product that will totally
> break my workflow.  Some day I may get used to having to email being
> sequestered behind both claret and cerulean oath2+sms 2fa layers, but
> for now I'll stick with keying in one password to receive an email vs.
> the required four.

So I appreciate this email coming from your old email address, but I
also just want to note that as long as you then use the oracle email
address for sending email, commit authorship, and "Signed-off-by:" (or
Acked-by etc) addresses, those tend to be the ones that _primarily_
get used when people then CC you on issues.

Well, at least that's how I work. The MAINTAINERS file tends to be the
secondary one.

But I wish you best of luck with the new email setup ;)

            Linus

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ