From: "Robin Jarry" <rjarry@redhat.com>
To: "Stephen Hemminger" <stephen@networkplumber.org>
Cc: <dev@dpdk.org>, "Thomas Monjalon" <thomas@monjalon.net>
Subject: Re: [PATCH] checkpatches: verify in-reply-to header when possible
Date: Mon, 07 Oct 2024 22:43:29 +0200 [thread overview]
Message-ID: <D4PV7AXOQ3NG.2P1Y88P3GLAK6@redhat.com> (raw)
In-Reply-To: <20241007134139.6ad8f94b@hermes.local>
Stephen Hemminger, Oct 07, 2024 at 22:41:
>> + && echo "$subject" | grep -qi 'v[2-9].*\]' \
>
> Your regex won't work for v10 etc.
Good catch. I'll send a v2.
next prev parent reply other threads:[~2024-10-07 20:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-05 15:35 Robin Jarry
2024-10-07 20:41 ` Stephen Hemminger
2024-10-07 20:43 ` Robin Jarry [this message]
2024-10-11 8:24 ` [PATCH dpdk v2] " Robin Jarry
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=D4PV7AXOQ3NG.2P1Y88P3GLAK6@redhat.com \
--to=rjarry@redhat.com \
--cc=dev@dpdk.org \
--cc=stephen@networkplumber.org \
--cc=thomas@monjalon.net \
/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;
as well as URLs for NNTP newsgroup(s).