From: Johan Hovold <johan@kernel.org>
To: Thorsten Leemhuis <linux@leemhuis.info>
Cc: Greg KH <gregkh@linuxfoundation.org>,
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 0/3] docs: stable-kernel-rules: add delayed backporting option and a few tweaks
Date: Tue, 11 Jul 2023 10:42:41 +0200 [thread overview]
Message-ID: <ZK0WAbB2P8wFWPCu@hovoldconsulting.com> (raw)
In-Reply-To: <29fb398b-a81c-70f9-f67c-21daaa42e4f7@leemhuis.info>
On Mon, Jul 10, 2023 at 07:18:43PM +0200, Thorsten Leemhuis wrote:
> On 10.07.23 19:10, Thorsten Leemhuis wrote:
> > * For patches that may have kernel version prerequisites specify them using
> > the following format in the sign-off area:
> >
> > .. code-block:: none
> >
> > Cc: <stable@vger.kernel.org> # 3.3.x
> >
> > The tag has the meaning of:
> >
> > .. code-block:: none
> >
> > git cherry-pick <this commit>
> >
> > For each "-stable" tree starting with the specified version.
>
> /me wonders if something like a "note, such tagging is unnecessary if
> the appropriate version can be derived from a Fixes: tag" would be
> appropriate and worth it here
Having these comments in the patch itself makes it easier to determine
whether a fix addresses a recent regression or an issue that's been
around since forever without having to copy-paste and look up each
commit in the Fixes tag(s).
Johan
next prev parent reply other threads:[~2023-07-11 8:42 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
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 [this message]
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=ZK0WAbB2P8wFWPCu@hovoldconsulting.com \
--to=johan@kernel.org \
--cc=corbet@lwn.net \
--cc=gregkh@linuxfoundation.org \
--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).