[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZK0WAbB2P8wFWPCu@hovoldconsulting.com>
Date: Tue, 11 Jul 2023 10:42:41 +0200
From: Johan Hovold <johan@...nel.org>
To: Thorsten Leemhuis <linux@...mhuis.info>
Cc: Greg KH <gregkh@...uxfoundation.org>, stable@...r.kernel.org,
linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
Sasha Levin <sashal@...nel.org>,
Jonathan Corbet <corbet@....net>
Subject: Re: [RFC PATCH v1 0/3] docs: stable-kernel-rules: add delayed
backporting option and a few tweaks
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@...r.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
Powered by blists - more mailing lists