On Thu, Feb 13, 2025 at 09:14:31PM +0100, Andrey Albershteyn wrote:
> These Cc: tags are intended for kernel commits which need to be
> backported to stable kernels. Maintainers of stable kernel aren't
> interested in xfsprogs syncs.
>
> Signed-off-by: Andrey Albershteyn <aalbersh@xxxxxxxxxx>
> ---
> tools/libxfs-apply | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/tools/libxfs-apply b/tools/libxfs-apply
> index 097a695f942bb832c2fb1456a0fd8c28c025d1a6..e9672e572d23af296dccfe6499eda9b909f44afd 100755
> --- a/tools/libxfs-apply
> +++ b/tools/libxfs-apply
> @@ -254,6 +254,7 @@ fixup_header_format()
> }
> /^Date:/ { date_seen=1; next }
> /^difflib/ { next }
> + /[Cc]{2}: <?stable@xxxxxxxxxxxxxxx>?.*/ { next }
You might want to ignore the angle brackets, because some people do:
Cc: stable@xxxxxxxxxxxxxxx
which is valid rfc822 even if SubmittingPatches says not to do that.
Annoyingly, other parts of the documentation lay that out as an example.
/[Cc]{2}:.*stable@xxxxxxxxxxxxxxx/ { next }
<shrug>
--D
>
> // {
> if (date_seen == 0)
>
> --
> 2.47.2
>
>
