All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thorsten Leemhuis <linux@leemhuis.info>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Sasha Levin <sashal@kernel.org>
Cc: Jonathan Corbet <corbet@lwn.net>,
	stable@vger.kernel.org, workflows@vger.kernel.org,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v1 0/4] docs: stable-kernel-rules: fine-tuning and 'no semi-automatic backport'
Date: Thu, 11 Apr 2024 07:25:02 +0200	[thread overview]
Message-ID: <cover.1712812895.git.linux@leemhuis.info> (raw)

After a recent discussion regarding "do we need a 'nobackport' tag" I
set out to create one change for stable-kernel-rules.rst.  This is now
the second patch in the series, which links to that discussion; the
other stuff is fine-tuning that happened along the way.

Ciao, Thorsten

Thorsten Leemhuis (4):
  docs: stable-kernel-rules: reduce redundancy
  docs: stable-kernel-rules: mention "no semi-automatic backport"
  docs: stable-kernel-rules: call mainline by its name and change
    example
  docs: stable-kernel-rules: remove code-labels tags

 Documentation/process/stable-kernel-rules.rst | 50 +++++++------------
 1 file changed, 18 insertions(+), 32 deletions(-)


base-commit: 3f86ed6ec0b390c033eae7f9c487a3fea268e027
-- 
2.44.0


             reply	other threads:[~2024-04-11  5:25 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-11  5:25 Thorsten Leemhuis [this message]
2024-04-11  5:25 ` [PATCH v1 1/4] docs: stable-kernel-rules: reduce redundancy Thorsten Leemhuis
2024-04-11  5:27   ` Greg Kroah-Hartman
2024-04-11  5:25 ` [PATCH v1 2/4] docs: stable-kernel-rules: mention "no semi-automatic backport" Thorsten Leemhuis
2024-04-11  5:29   ` Greg Kroah-Hartman
2024-04-11  6:59     ` Thorsten Leemhuis
2024-04-11  7:40       ` Greg Kroah-Hartman
2024-04-11  7:50         ` Thorsten Leemhuis
2024-04-11  9:13           ` Greg Kroah-Hartman
2024-04-11  9:19             ` Geert Uytterhoeven
2024-04-11  9:53               ` Greg Kroah-Hartman
2024-04-11  9:57               ` Thorsten Leemhuis
2024-04-11 15:12                 ` Greg Kroah-Hartman
2024-04-11  5:25 ` [PATCH v1 3/4] docs: stable-kernel-rules: call mainline by its name and change example Thorsten Leemhuis
2024-04-11  5:30   ` Greg Kroah-Hartman
2024-04-11  5:50     ` Thorsten Leemhuis
2024-04-11  6:10       ` Greg Kroah-Hartman
2024-04-11  6:50         ` Thorsten Leemhuis
2024-04-11  6:56           ` Greg Kroah-Hartman
2024-04-11  7:18             ` Thorsten Leemhuis
2024-04-11  5:25 ` [PATCH v1 4/4] docs: stable-kernel-rules: remove code-labels tags Thorsten Leemhuis
2024-04-11  5:31   ` Greg Kroah-Hartman

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.1712812895.git.linux@leemhuis.info \
    --to=linux@leemhuis.info \
    --cc=corbet@lwn.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sashal@kernel.org \
    --cc=stable@vger.kernel.org \
    --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 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.