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: <o552411n-nn6s-q3rp-nrp8-2669so1s868s@xreary.bet>
Date: Sat, 24 Jan 2026 23:47:13 +0100 (CET)
From: Jiri Kosina <jikos@...nel.org>
To: Linus Torvalds <torvalds@...ux-foundation.org>
cc: Dan Williams <dan.j.williams@...el.com>, 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 Sat, 24 Jan 2026, Linus Torvalds 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...

FWIW

	Reviewed-by: Jiri Kosina <jkosina@...e.com>

(or Supported-by:, or whatnot).

Thanks,

-- 
Jiri Kosina
SUSE Labs