From: David Marchand <david.marchand@redhat.com>
To: luca.boccassi@gmail.com
Cc: dev@dpdk.org, thomas@monjalon.net, maxime.coquelin@redhat.com,
ktraynor@redhat.com, Luca Boccassi <bluca@debian.org>,
Stephen Hemminger <stephen@networkplumber.org>
Subject: Re: [PATCH] doc: relax requirement on commit messages of security fixes
Date: Fri, 24 Nov 2023 14:53:20 +0100 [thread overview]
Message-ID: <CAJFAV8x_yCD=4jkhS+2wL7N0bWfPAZz9Tfxe=xrD18FtNJ7MeA@mail.gmail.com> (raw)
In-Reply-To: <20220310175947.273850-1-luca.boccassi@gmail.com>
On Thu, Mar 10, 2022 at 7:00 PM <luca.boccassi@gmail.com> wrote:
>
> From: Luca Boccassi <bluca@debian.org>
>
> Allow more flexibility with embargo lifting by not requiring
> mentions of CVEs in commit messages if the lift date allows
> it.
>
> Signed-off-by: Luca Boccassi <bluca@debian.org>
Applied, thanks Luca.
--
David Marchand
prev parent reply other threads:[~2023-11-24 13:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-10 17:59 luca.boccassi
2023-03-31 10:34 ` Thomas Monjalon
2023-03-31 10:37 ` Maxime Coquelin
2023-07-05 23:07 ` Stephen Hemminger
2023-11-24 13:53 ` David Marchand [this message]
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='CAJFAV8x_yCD=4jkhS+2wL7N0bWfPAZz9Tfxe=xrD18FtNJ7MeA@mail.gmail.com' \
--to=david.marchand@redhat.com \
--cc=bluca@debian.org \
--cc=dev@dpdk.org \
--cc=ktraynor@redhat.com \
--cc=luca.boccassi@gmail.com \
--cc=maxime.coquelin@redhat.com \
--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).