From: Thorsten Leemhuis <linux@leemhuis.info>
To: Greg KH <gregkh@linuxfoundation.org>, stable@vger.kernel.org
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v1 0/5] docs: stable-kernel-rules: improve structure and a few tweaks
Date: Sat, 5 Aug 2023 09:21:28 +0200 [thread overview]
Message-ID: <cover.1691219455.git.linux@leemhuis.info> (raw)
When adding something to this document earlier I noticed that readers
need to perform some back and forth to fully understand things; I also
noticed a few other aspects that seemed somewhat odd for me with my
background on writing and editing texts.
Find attached a few patches to improve things. The first three are
mainly moving text around to a structure which is somewhat clearer. They
leave quite a few rough edges behind that are fixed in in the last patch
of the series, which changes a few other changes as well; thx to the
prep patches the diff should be relative straight-forward to understand.
These patches are on-top of the following series that currently is in the
driver-core-testing branch:
https://lore.kernel.org/all/cover.1689056247.git.linux@leemhuis.info/
Ciao, Thorsten
v1:
* new patch-set based on patch 3/3 and other feedback to the following
patchset[1], but slit off into a seperate set with four distinct
patches to make it easier to see what is actually changed
https://lore.kernel.org/linux-doc/d30686781c47c83927e0a41f6a1167a679fa822c.1689008220.git.linux@leemhuis.info/
* append one more patch for something that came up
Thorsten Leemhuis (5):
docs: stable-kernel-rules: improve structure by changing headlines
docs: stable-kernel-rules: move text around to improve flow
docs: stable-kernel-rules: make the examples for option 1 a proper
list
docs: stable-kernel-rules: fine-tune various details
docs: stable-kernel-rules: mention that regressions must be prevented
Documentation/process/stable-kernel-rules.rst | 165 ++++++++++--------
1 file changed, 91 insertions(+), 74 deletions(-)
base-commit: 016571b6d52deb473676fb4d24baf8ed3667ae21
prerequisite-patch-id: b00970f680f3032fe8a7d0e3843b76d60c2f0458
prerequisite-patch-id: 9926a13726e99d51800f52cb84e26ae971757467
--
2.40.1
next reply other threads:[~2023-08-05 7:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-05 7:21 Thorsten Leemhuis [this message]
2023-08-05 7:21 ` [PATCH v1 1/5] docs: stable-kernel-rules: improve structure by changing headlines Thorsten Leemhuis
2023-08-05 7:21 ` [PATCH v1 2/5] docs: stable-kernel-rules: move text around to improve flow Thorsten Leemhuis
2023-08-05 7:21 ` [PATCH v1 3/5] docs: stable-kernel-rules: make the examples for option 1 a proper list Thorsten Leemhuis
2023-08-05 7:21 ` [PATCH v1 4/5] docs: stable-kernel-rules: fine-tune various details Thorsten Leemhuis
2023-08-05 7:21 ` [PATCH v1 5/5] docs: stable-kernel-rules: mention that regressions must be prevented Thorsten Leemhuis
2023-08-05 7:54 ` [PATCH v1 0/5] docs: stable-kernel-rules: improve structure and a few tweaks Thorsten Leemhuis
2023-08-12 11:03 ` Greg KH
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=cover.1691219455.git.linux@leemhuis.info \
--to=linux@leemhuis.info \
--cc=gregkh@linuxfoundation.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@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