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/[email protected]/ [1] Link: https://lore.kernel.org/all/[email protected]/ [2] Link: https://lore.kernel.org/all/[email protected]/ [3] Signed-off-by: Thorsten Leemhuis <[email protected]> --- A patch to make one of the stable-script honor the flag can be found in https://lore.kernel.org/all/[email protected]/ 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: <[email protected]> # 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: <[email protected]> # reason goes here, and must be present + .. _option_2: Option 2 -- 2.44.0
