linux-kernel - Re: [PATCH] Documentation: Project continuity

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: <CAHk-=whUg3js1GV4f0dmC+nvJbiNfsM7QZv7k8Q6AoFUfeH-KQ@mail.gmail.com>
Date: Sat, 24 Jan 2026 14:43:05 -0800
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Dan Williams <dan.j.williams@...el.com>
Cc: corbet@....net, ksummit@...ts.linux.dev, linux-kernel@...r.kernel.org, 
	tech-board-discuss@...ts.linux.dev, 
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>, Miguel Ojeda <ojeda@...nel.org>, 
	Kees Cook <kees@...nel.org>
Subject: Re: [PATCH] Documentation: Project continuity

On Fri, 23 Jan 2026 at 17:21, Dan Williams <dan.j.williams@...el.com> wrote:
>
> Document project continuity procedures.

I think I'll just commit this as-is, and directly.

Sure, it could just go through the doc tree, and that would be
"standard procedure", but when it comes to something like this, I
think it looks better to just have me commit it myself than have me
pull it from some other source.

Any future updates from further discussion can then go through the doc
tree as normal...

            Linus