From: Jiri Kosina <jikos@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.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,
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 23:47:13 +0100 (CET) [thread overview]
Message-ID: <o552411n-nn6s-q3rp-nrp8-2669so1s868s@xreary.bet> (raw)
In-Reply-To: <CAHk-=whUg3js1GV4f0dmC+nvJbiNfsM7QZv7k8Q6AoFUfeH-KQ@mail.gmail.com>
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@suse.com>
(or Supported-by:, or whatnot).
Thanks,
--
Jiri Kosina
SUSE Labs
next prev parent reply other threads:[~2026-01-24 22:47 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
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 [this message]
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=o552411n-nn6s-q3rp-nrp8-2669so1s868s@xreary.bet \
--to=jikos@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox