Some developers deliberately steer clear of 'Fixes:' tags to prevent changes from being backported semi-automatically by the stable team. That somewhat undermines the reason for the existence of the Fixes: tag, hence point out there is an alternative to reach the same effect. Link: https://lore.kernel.org/all/dfd87673-c581-4b4b-b37a-1cf5c817240d@xxxxxxxxxxxxx/ Signed-off-by: Thorsten Leemhuis <linux@xxxxxxxxxxxxx> --- 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 7bb16d42a51833..ebd57cb9277f7b 100644 --- a/Documentation/process/stable-kernel-rules.rst +++ b/Documentation/process/stable-kernel-rules.rst @@ -117,6 +117,12 @@ comment to pass arbitrary or predefined notes: Note, such tagging is unnecessary if the stable team can derive the appropriate versions from Fixes: tags. + * Prevent semi-automatic backporting of changes carrying a 'Fixes:' tag: + + .. code-block:: none + + Cc: <stable@xxxxxxxxxxxxxxx> # no semi-automatic backport + * Delay pick up of patches: .. code-block:: none -- 2.44.0
