ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Cc: Dan Williams <dan.j.williams@intel.com>,
	corbet@lwn.net, ksummit@lists.linux.dev,
	linux-kernel@vger.kernel.org, tech-board-discuss@lists.linux.dev,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Miguel Ojeda <ojeda@kernel.org>, Kees Cook <kees@kernel.org>
Subject: Re: [PATCH] Documentation: Project continuity
Date: Sat, 24 Jan 2026 10:31:23 +0100	[thread overview]
Message-ID: <2026012441-jolliness-cringing-7e9f@gregkh> (raw)
In-Reply-To: <20260124082939.40715e13@foz.lan>

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@intel.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

  reply	other threads:[~2026-01-24  9:31 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-24  1:22 Dan Williams
2026-01-24  7:29 ` Mauro Carvalho Chehab
2026-01-24  9:31   ` Greg Kroah-Hartman [this message]
2026-01-24 11:17   ` Miguel Ojeda
2026-01-24 20:45   ` Jiri Kosina
2026-01-24 22:43 ` Linus Torvalds
2026-01-24 22:47   ` Jiri Kosina
2026-01-24 23:58 ` Steven Rostedt
2026-01-26  2:08 ` Shuah
2026-01-26  3:19 ` Julia Lawall
2026-01-27 14:34 ` Linus Walleij

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2026012441-jolliness-cringing-7e9f@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=corbet@lwn.net \
    --cc=dan.j.williams@intel.com \
    --cc=kees@kernel.org \
    --cc=ksummit@lists.linux.dev \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mchehab+huawei@kernel.org \
    --cc=ojeda@kernel.org \
    --cc=tech-board-discuss@lists.linux.dev \
    --cc=torvalds@linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox