From: Jonathan Corbet <corbet@lwn.net>
To: Lukas Bulwahn <lukas.bulwahn@gmail.com>,
workflows@vger.kernel.org, linux-doc@vger.kernel.org
Cc: kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org,
Lukas Bulwahn <lukas.bulwahn@gmail.com>
Subject: Re: [PATCH] docs: submit-checklist: structure by category
Date: Wed, 28 Feb 2024 14:57:19 -0700 [thread overview]
Message-ID: <87h6hsp800.fsf@meer.lwn.net> (raw)
In-Reply-To: <20240226104653.54877-1-lukas.bulwahn@gmail.com>
Lukas Bulwahn <lukas.bulwahn@gmail.com> writes:
> While going through the submit checklist, the list order seemed rather
> random, probably just by historical coincidences of always adding yet the
> next point someone thought of at the end of the list.
>
> Structure and order them by the category of such activity,
> reviewing, documenting, checking with tools, building and testing.
So this is clearly a step in the right direction, so I'm not opposed to
it. But I do have a couple of thoughts:
- This document is old and unloved. Its age shows in a lot of ways
(wmb() rather than the sorts of barriers that are socially acceptable
in 2024, for example). It makes no mention of the CI systems that
should get their say for a lot of subsystems; nor does it mention the
subsystem-specific maintainer profiles that should also be
consulted. And so on. It needs a lot of work rather than a
reshuffling. (But, as I say, the reshuffling is an improvement, so
I'll take it).
- It's a bit of an awkward fit with submitting-patches.rst. Someday
we'll have a set of coherent docs, maybe.
Anyway, I'm done grumbling now...:) I'll look forward to v2 -
preferably soon; I have travel coming up and may need to cut things off
for 6.9 a bit earlier than usual.
Thanks,
jon
next prev parent reply other threads:[~2024-02-28 21:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-26 10:46 [PATCH] docs: submit-checklist: structure by category Lukas Bulwahn
2024-02-26 12:48 ` Jani Nikula
2024-02-27 7:28 ` Lukas Bulwahn
2024-02-27 0:41 ` Randy Dunlap
2024-02-27 8:04 ` Lukas Bulwahn
2024-02-27 8:57 ` Geert Uytterhoeven
2024-02-27 11:03 ` Lukas Bulwahn
2024-02-27 11:24 ` Geert Uytterhoeven
2024-02-28 21:57 ` Jonathan Corbet [this message]
2024-02-28 23:03 ` Randy Dunlap
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=87h6hsp800.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.bulwahn@gmail.com \
--cc=workflows@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).