From: Steven Rostedt <rostedt@goodmis.org>
To: Dan Williams <dan.j.williams@intel.com>
Cc: corbet@lwn.net, ksummit@lists.linux.dev,
linux-kernel@vger.kernel.org, tech-board-discuss@lists.linux.dev,
Linus Torvalds <torvalds@linux-foundation.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Miguel Ojeda <ojeda@kernel.org>, Kees Cook <kees@kernel.org>
Subject: Re: [PATCH] Documentation: Project continuity
Date: Sat, 24 Jan 2026 18:58:14 -0500 [thread overview]
Message-ID: <20260124185814.513d3aab@robin> (raw)
In-Reply-To: <20260124012256.1856709-1-dan.j.williams@intel.com>
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].
>
> Cc: Linus Torvalds <torvalds@linux-foundation.org>
> Co-developed-by: Jonathan Corbet <corbet@lwn.net>
> Signed-off-by: Jonathan Corbet <corbet@lwn.net>
> Reviewed-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> Reviewed-by: Miguel Ojeda <ojeda@kernel.org>
> Reviewed-by: Kees Cook <kees@kernel.org>
> Link: https://lwn.net/Articles/1050179/ [1]
> Signed-off-by: Dan Williams <dan.j.williams@intel.com>
I thought I sent this out earlier, but anyway...
Reviewed-by: Steven Rostedt <rostedt@goodmis.org>
-- Steve
next prev parent reply other threads:[~2026-01-24 23:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-24 1:22 [PATCH] Documentation: Project continuity Dan Williams
2026-01-24 7:29 ` Mauro Carvalho Chehab
2026-01-24 9:31 ` Greg Kroah-Hartman
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 [this message]
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=20260124185814.513d3aab@robin \
--to=rostedt@goodmis.org \
--cc=corbet@lwn.net \
--cc=dan.j.williams@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=kees@kernel.org \
--cc=ksummit@lists.linux.dev \
--cc=linux-kernel@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.