From: Greg KH <gregkh@linuxfoundation.org>
To: "Toke Høiland-Jørgensen" <toke@redhat.com>
Cc: workflows@vger.kernel.org
Subject: Re: Selective lei filters and replies to old threads
Date: Thu, 24 Aug 2023 19:11:14 +0200 [thread overview]
Message-ID: <2023082415-elongated-cogwheel-8465@gregkh> (raw)
In-Reply-To: <87msyob551.fsf@toke.dk>
On Fri, Aug 18, 2023 at 08:02:34PM +0200, Toke Høiland-Jørgensen wrote:
> Greg KH <gregkh@linuxfoundation.org> writes:
>
> > On Thu, Aug 17, 2023 at 04:15:54PM +0200, Toke Høiland-Jørgensen wrote:
> >> [0] Side note: if anyone has a nice trick to specifically exclude Greg's
> >> stable patch bombs from this, I would be interested in hearing about
> >> that as well :)
> >
> > I thought those stable patch bombs had a X- header on them, like:
> > X-stable: review
> > and
> > X-Patchwork-Hint: ignore
> > but somehow it looks like I'm only adding that to the first message in
> > the stable-patch-bomb series.
> >
> > Would it help for me to fix my side and add those headers to make it
> > easier for you to be able to ignore them?
>
> I don't think it's possible to match on arbitrary headers in Lore
> searches (maybe public-inbox could be taught that?), but it would
> certainly aid in adding local filtering after fetching which would work
> for me as a workaround. So yes, please! :)
Turned out my scripts were broken, and the header I was supposed to be
putting on all stable patches was no longer happening (something changed
in git format-patch's output I think.)
So this should be now fixed up with the latest 5.10.192-rc1 announcement
and emails.
thanks,
greg k-h
next prev parent reply other threads:[~2023-08-24 17:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-17 14:15 Toke Høiland-Jørgensen
2023-08-17 20:47 ` Greg KH
2023-08-18 18:02 ` Toke Høiland-Jørgensen
2023-08-24 17:11 ` Greg KH [this message]
2023-08-24 18:04 ` Toke Høiland-Jørgensen
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=2023082415-elongated-cogwheel-8465@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=toke@redhat.com \
--cc=workflows@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox