All of lore.kernel.org
 help / color / mirror / Atom feed
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 v2 0/2] docs: stable-kernel-rules: add delayed backporting option and a few tweaks
Date: Tue, 11 Jul 2023 08:19:52 +0200	[thread overview]
Message-ID: <cover.1689056247.git.linux@leemhuis.info> (raw)

I only set down to create the first of the two patches. But while
doing so I noticed a few things that seemed odd for me with my
background on writing and editing texts. So I just quickly performed a
few additional changes to fix those to see if the stable team would
appreciate them, as this document is clearly their domain.

v2:
[this mail]
* a few small tweaks after feedback from v1 submission
* drop patch 3 for now
* drop RFC

v1:
https://lore.kernel.org/linux-doc/d30686781c47c83927e0a41f6a1167a679fa822c.1689008220.git.linux@leemhuis.info/

Thorsten Leemhuis (2):
  docs: stable-kernel-rules: mention other usages for stable tag
    comments
  docs: stable-kernel-rules: make rule section more straight forward

 Documentation/process/stable-kernel-rules.rst | 60 ++++++++++++-------
 1 file changed, 37 insertions(+), 23 deletions(-)


base-commit: 016571b6d52deb473676fb4d24baf8ed3667ae21
-- 
2.40.1


             reply	other threads:[~2023-07-11  6:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-11  6:19 Thorsten Leemhuis [this message]
2023-07-11  6:19 ` [PATCH v2 1/2] docs: stable-kernel-rules: mention other usages for stable tag comments Thorsten Leemhuis
2023-07-11  6:19 ` [PATCH v2 2/2] docs: stable-kernel-rules: make rule section more straight forward 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=cover.1689056247.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.