[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2026012441-jolliness-cringing-7e9f@gregkh>
Date: Sat, 24 Jan 2026 10:31:23 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Mauro Carvalho Chehab <mchehab+huawei@...nel.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,
Linus Torvalds <torvalds@...ux-foundation.org>,
Miguel Ojeda <ojeda@...nel.org>, Kees Cook <kees@...nel.org>
Subject: Re: [PATCH] Documentation: Project continuity
On Sat, Jan 24, 2026 at 08:29:39AM +0100, Mauro Carvalho Chehab wrote:
> On Fri, 23 Jan 2026 17:22:56 -0800
> Dan Williams <dan.j.williams@...el.com> wrote:
>
> > Document project continuity procedures. This is a plan for a plan for
> > navigating events that affect the forward progress of the canonical Linux
> > repository, torvalds/linux.git. It is a follow-up from Maintainer Summit
> > [1].
>
> The idea behind this document is interesting, but IMHO it is too
> optimistic for a contingency plan ;-)
>
> Conceptually, contingency plans are written to overcome all foreseeable
> bad consequences that might happen. So, it should include backups
> for each possible bad scenario.
That is not the goal here, we aren't going to enumerate all of the
potential issues/plans for every possible scenario, that's just
impossible and would take forever and likely result in something that is
unworkable. This is here to say "these are the steps we will take to
form a future plan if something goes wrong with our current one."
thanks,
greg k-h
Powered by blists - more mailing lists