From: Stephen Hemminger <stephen@networkplumber.org>
To: Maxime Coquelin <maxime.coquelin@redhat.com>
Cc: Thomas Monjalon <thomas@monjalon.net>,
dev@dpdk.org, david.marchand@redhat.com, ktraynor@redhat.com,
Luca Boccassi <bluca@debian.org>,
luca.boccassi@gmail.com,
Christian Ehrhardt <christian.ehrhardt@canonical.com>,
xuemingl@nvidia.com
Subject: Re: [PATCH] doc: relax requirement on commit messages of security fixes
Date: Wed, 5 Jul 2023 16:07:02 -0700 [thread overview]
Message-ID: <20230705160702.3b46a42e@hermes.local> (raw)
In-Reply-To: <f6532cd0-b88f-cafc-7d46-804641bc5c4d@redhat.com>
On Fri, 31 Mar 2023 12:37:40 +0200
Maxime Coquelin <maxime.coquelin@redhat.com> wrote:
> Indeed!
>
> On 3/31/23 12:34, Thomas Monjalon wrote:
> > We missed this patch, there was no comment.
> > Please review.
> >
> > 10/03/2022 18:59, luca.boccassi@gmail.com:
> >> 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>
> >> ---
> >> -The CVE id and the bug id must be referenced in the patch.
> >> +The CVE id and the bug id must be referenced in the patch if there is no
> >> +embargo, or if there is an embargo, but it will be lifted when the release
> >> +including the patch is published. If the embargo is going to be lifted after the
> >> +release, then the CVE and bug ids must be omitted from the commit message.
> >
> >
>
> Reviewed-by: Maxime Coquelin <maxime.coquelin@redhat.com>
Acked-by: Stephen Hemminger <stephen@networkplumber.org>
next prev parent reply other threads:[~2023-07-05 23:07 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 [this message]
2023-11-24 13:53 ` David Marchand
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=20230705160702.3b46a42e@hermes.local \
--to=stephen@networkplumber.org \
--cc=bluca@debian.org \
--cc=christian.ehrhardt@canonical.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=ktraynor@redhat.com \
--cc=luca.boccassi@gmail.com \
--cc=maxime.coquelin@redhat.com \
--cc=thomas@monjalon.net \
--cc=xuemingl@nvidia.com \
/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).