public inbox for linux-doc@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Thorsten Leemhuis <linux@leemhuis.info>
Cc: stable@vger.kernel.org, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org, Sasha Levin <sashal@kernel.org>,
	Jonathan Corbet <corbet@lwn.net>
Subject: Re: [PATCH v1 0/5] docs: stable-kernel-rules: improve structure and a few tweaks
Date: Sat, 12 Aug 2023 13:03:46 +0200	[thread overview]
Message-ID: <2023081237-sulphate-fifteen-0c18@gregkh> (raw)
In-Reply-To: <63380dd3-bce5-d295-ab14-13102f402c73@leemhuis.info>

On Sat, Aug 05, 2023 at 09:54:25AM +0200, Thorsten Leemhuis wrote:
> [adding Sasha and Jon to the CC, seem I forget to do that on the cover
> letter; sorry!]
> 
> On 05.08.23 09:21, Thorsten Leemhuis wrote:
> > 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/
> 
> FWIW, in case anyone wonders how the text looks in the end, see:
> 
> https://www.leemhuis.info/files/kernel/stable-rules/stable-kernel-rules.txt
> 
> https://www.leemhuis.info/files/kernel/stable-rules/Everything%20you%20ever%20wanted%20to%20know%20about%20Linux%20-stable%20releases%20%e2%80%94%20The%20Linux%20Kernel%20documentation.html

Looks very good, thanks!

greg k-h

      reply	other threads:[~2023-08-12 11:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-05  7:21 [PATCH v1 0/5] docs: stable-kernel-rules: improve structure and a few tweaks Thorsten Leemhuis
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 [this message]

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=2023081237-sulphate-fifteen-0c18@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@leemhuis.info \
    --cc=sashal@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