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: [RFC PATCH v1 3/3] docs: stable-kernel-rules: improve structure to optimize reading flow
Date: Mon, 10 Jul 2023 21:46:15 +0200 [thread overview]
Message-ID: <2023071035-pristine-plus-0c11@gregkh> (raw)
In-Reply-To: <e25941af193a99b70ee27fcbaa61974fc63a50fd.1689008220.git.linux@leemhuis.info>
On Mon, Jul 10, 2023 at 07:10:13PM +0200, Thorsten Leemhuis wrote:
> Optimize the text flow to make things more straight forward to follow:
>
> * remove a subheading without real purpose
> * after outlining the three options add a section that explains them in
> more detail; move the "Following the submission" text that set in the
> middle of this to a later place in the document
> * a few small clarifications along the way
All of this churn makes it really hard to determine what the end result
is. Do you have a before/after result anywhere?
Or maybe split this out into 3 different patches?
thanks,
greg k-h
next prev parent reply other threads:[~2023-07-10 19:46 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-10 17:10 [RFC PATCH v1 0/3] docs: stable-kernel-rules: add delayed backporting option and a few tweaks Thorsten Leemhuis
2023-07-10 17:10 ` [RFC PATCH v1 1/3] docs: stable-kernel-rules: mention other usages for stable tag comments Thorsten Leemhuis
2023-07-10 19:43 ` Greg KH
2023-07-11 6:07 ` Thorsten Leemhuis
2023-07-11 10:15 ` Jani Nikula
2023-07-11 10:33 ` Thorsten Leemhuis
2023-07-10 17:10 ` [RFC PATCH v1 2/3] docs: stable-kernel-rules: make rule section more straight forward Thorsten Leemhuis
2023-07-10 19:44 ` Greg KH
2023-07-10 17:10 ` [RFC PATCH v1 3/3] docs: stable-kernel-rules: improve structure to optimize reading flow Thorsten Leemhuis
2023-07-10 19:46 ` Greg KH [this message]
2023-07-10 17:18 ` [RFC PATCH v1 0/3] docs: stable-kernel-rules: add delayed backporting option and a few tweaks Thorsten Leemhuis
2023-07-10 19:50 ` Greg KH
2023-07-11 5:57 ` Thorsten Leemhuis
2023-07-11 8:42 ` Johan Hovold
2023-07-11 8:57 ` Thorsten Leemhuis
2023-07-10 19:51 ` Greg KH
2023-07-12 9:30 ` Thorsten Leemhuis
2023-07-12 15:16 ` Greg KH
2023-07-12 17:02 ` Thorsten Leemhuis
2023-07-12 19:00 ` Greg KH
2023-07-13 8:48 ` Thorsten Leemhuis
2023-07-13 15:06 ` Greg KH
2023-07-13 15:39 ` Conor Dooley
2023-07-13 16:27 ` Thorsten Leemhuis
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=2023071035-pristine-plus-0c11@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;
as well as URLs for NNTP newsgroup(s).