From: "Darrick J. Wong" <djwong@kernel.org>
To: Andrey Albershteyn <aalbersh@redhat.com>
Cc: linux-xfs@vger.kernel.org, Andrey Albershteyn <aalbersh@kernel.org>
Subject: Re: [PATCH v4 09/10] libxfs-apply: drop Cc: to stable release list
Date: Thu, 13 Feb 2025 14:47:40 -0800 [thread overview]
Message-ID: <20250213224740.GW21808@frogsfrogsfrogs> (raw)
In-Reply-To: <2yzj7wrqodq7d5tt6mcj2yrplgf3kwt34ewl2y3rpcizan4gzb@rj6b2agkbhre>
On Thu, Feb 13, 2025 at 11:27:06PM +0100, Andrey Albershteyn wrote:
> On 2025-02-13 13:45:41, Darrick J. Wong wrote:
> > 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@kernel.org>
> > > ---
> > > 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@vger.kernel.org>?.*/ { next }
> >
> > You might want to ignore the angle brackets, because some people do:
>
> The ? does that :) One or zero of <>
Aha, I missed that! Thanks for the correction.
Reviewed-by: "Darrick J. Wong" <djwong@kernel.org>
--D
> >
> > Cc: stable@vger.kernel.org
> >
> > 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@vger.kernel.org/ { next }
> >
> > <shrug>
> >
> > --D
> >
> > >
> > > // {
> > > if (date_seen == 0)
> > >
> > > --
> > > 2.47.2
> > >
> > >
> >
>
> --
> - Andrey
>
>
next prev parent reply other threads:[~2025-02-13 22:47 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-13 20:14 [PATCH v4 00/10] Update release.sh Andrey Albershteyn
2025-02-13 20:14 ` [PATCH v4 01/10] release.sh: add signing and fix outdated commands Andrey Albershteyn
2025-02-13 20:14 ` [PATCH v4 02/10] release.sh: add --kup to upload release tarball to kernel.org Andrey Albershteyn
2025-02-13 20:14 ` [PATCH v4 03/10] release.sh: update version files make commit optional Andrey Albershteyn
2025-02-13 20:14 ` [PATCH v4 04/10] Add git-contributors script to notify about merges Andrey Albershteyn
2025-02-13 20:14 ` [PATCH v4 05/10] git-contributors: better handling of hash mark/multiple emails Andrey Albershteyn
2025-02-13 21:47 ` Darrick J. Wong
2025-02-13 20:14 ` [PATCH v4 06/10] git-contributors: make revspec required and shebang fix Andrey Albershteyn
2025-02-13 21:45 ` Darrick J. Wong
2025-02-13 20:14 ` [PATCH v4 07/10] release.sh: generate ANNOUNCE email Andrey Albershteyn
2025-02-13 20:14 ` [PATCH v4 08/10] release.sh: add -f to generate for-next update email Andrey Albershteyn
2025-02-13 20:14 ` [PATCH v4 09/10] libxfs-apply: drop Cc: to stable release list Andrey Albershteyn
2025-02-13 21:45 ` Darrick J. Wong
2025-02-13 22:27 ` Andrey Albershteyn
2025-02-13 22:47 ` Darrick J. Wong [this message]
2025-02-13 20:14 ` [PATCH v4 10/10] gitignore: ignore a few newly generated files Andrey Albershteyn
2025-02-13 20:20 ` Darrick J. Wong
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250213224740.GW21808@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=aalbersh@kernel.org \
--cc=aalbersh@redhat.com \
--cc=linux-xfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.