On Mon, Apr 29, 2024 at 09:18:30AM +0200, Thorsten Leemhuis wrote:
> Document a new variant of the stable tag developers can use to make the
> stable team's tools ignore a change[1].
> 
> That way developers can use 'Fixes:' tags without fearing the changes
> might be backported in semi-automatic fashion. Such concerns are the
> reason why some developers deliberately omit the 'Fixes:' tag in
> changes[2] -- which somewhat undermines the reason for the existence of
> that tag and might be unwise in the long term[3].
> 
> Link: 
> https://lore.kernel.org/all/b452fd54-fdc6-47e4-8c26-6627f6b7e...@leemhuis.info/
>  [1]
> Link: 
> https://lore.kernel.org/all/cover.1712226175.git.antony.ant...@secunet.com/ 
> [2]
> Link: 
> https://lore.kernel.org/all/dfd87673-c581-4b4b-b37a-1cf5c8172...@leemhuis.info/
>  [3]
> Signed-off-by: Thorsten Leemhuis <li...@leemhuis.info>
> 
> ---
> 
> A patch to make one of the stable-script honor the flag can be found in
> https://lore.kernel.org/all/655ce2a3-eb04-4ade-999e-23fc5dc5f...@leemhuis.info/
> 
> For autosel I was unable to locate the code.
> ---
>  Documentation/process/stable-kernel-rules.rst | 6 ++++++
>  1 file changed, 6 insertions(+)
> 
> diff --git a/Documentation/process/stable-kernel-rules.rst 
> b/Documentation/process/stable-kernel-rules.rst
> index ebf4152659f2d0..9ca8083b41c7f1 100644
> --- a/Documentation/process/stable-kernel-rules.rst
> +++ b/Documentation/process/stable-kernel-rules.rst
> @@ -129,6 +129,12 @@ comment to pass arbitrary or predefined notes:
>  
>      Cc: <sta...@vger.kernel.org> # see patch description, needs adjustments 
> for <= 6.3
>  
> +There furthermore is a variant of the stable tag you can use to make the 
> stable
> +team's backporting tools (e.g AUTOSEL or scripts that look for commits
> +containing a 'Fixes:' tag) ignore a change::
> +
> +     Cc: <stable+noauto...@kernel.org> # reason goes here, and must be 
> present
> +
>  .. _option_2:
>  

Thanks for seeing this through:

Reviewed-by: Greg Kroah-Hartman <gre...@linuxfoundation.org>

Reply via email to