workflows.vger.kernel.org archive mirror
 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 v2 0/5] docs: stable-kernel-rules: fine-tuning and 'no stable backport' tag
Date: Mon, 29 Apr 2024 09:18:25 +0200	[thread overview]
Message-ID: <cover.1714367921.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 last patch in the series, which links to that discussion with
all the details; the other stuff is fine-tuning that happened along the
way.

Ciao, Thorsten
---
v1->v2:
* Add reviewed-by tag from Greg to the first patch.
* Change the backport example in 2 as suggested by Greg.
* Improve description of patch 3 while also making the change remove a
  level of indenting.
* Add patch explaining stable@kernel.org (w/o @vger.)
* Move the patch adding a 'make AUTOSEL et. al. ignore a change' flag to
  the end of the series and use stable+noautosel@kernel.org as
  suggested my Konstantin and ACKed by Greg.

v1: https://lore.kernel.org/all/cover.1712812895.git.linux@leemhuis.info/

Thorsten Leemhuis (5):
  docs: stable-kernel-rules: reduce redundancy
  docs: stable-kernel-rules: call mainline by its name and change
    example
  docs: stable-kernel-rules: remove code-labels tags and a indention
    level
  docs: stable-kernel-rules: explain use of stable@kernel.org (w/o
    @vger.)
  docs: stable-kernel-rules: create special tag to flag 'no backporting'

 Documentation/process/stable-kernel-rules.rst | 234 ++++++++----------
 1 file changed, 110 insertions(+), 124 deletions(-)


base-commit: 5eb4573ea63d0c83bf58fb7c243fc2c2b6966c02
-- 
2.44.0


             reply	other threads:[~2024-04-29  7:18 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-29  7:18 Thorsten Leemhuis [this message]
2024-04-29  7:18 ` [PATCH v2 1/5] docs: stable-kernel-rules: reduce redundancy Thorsten Leemhuis
2024-04-29  7:18 ` [PATCH v2 2/5] docs: stable-kernel-rules: call mainline by its name and change example Thorsten Leemhuis
2024-04-29  7:49   ` Greg Kroah-Hartman
2024-04-29  7:18 ` [PATCH v2 3/5] docs: stable-kernel-rules: remove code-labels tags and a indention level Thorsten Leemhuis
2024-04-29  7:49   ` Greg Kroah-Hartman
2024-04-29  7:18 ` [PATCH v2 4/5] docs: stable-kernel-rules: explain use of stable@kernel.org (w/o @vger.) Thorsten Leemhuis
2024-04-29  7:51   ` Greg Kroah-Hartman
2024-04-29  8:30     ` Thorsten Leemhuis
2024-04-29  8:36       ` Greg Kroah-Hartman
2024-04-29  7:18 ` [PATCH v2 5/5] docs: stable-kernel-rules: create special tag to flag 'no backporting' Thorsten Leemhuis
2024-04-29  7:51   ` Greg Kroah-Hartman
2024-05-02 16:13 ` [PATCH v2 0/5] docs: stable-kernel-rules: fine-tuning and 'no stable backport' tag Jonathan Corbet

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.1714367921.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 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).