All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: dev@dpdk.org
Cc: maxime.coquelin@redhat.com, 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: Fri, 31 Mar 2023 12:34:47 +0200	[thread overview]
Message-ID: <5508921.CQOukoFCf9@thomas> (raw)
In-Reply-To: <20220310175947.273850-1-luca.boccassi@gmail.com>

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.



  reply	other threads:[~2023-03-31 10:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-10 17:59 [PATCH] doc: relax requirement on commit messages of security fixes luca.boccassi
2023-03-31 10:34 ` Thomas Monjalon [this message]
2023-03-31 10:37   ` Maxime Coquelin
2023-07-05 23:07     ` Stephen Hemminger
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=5508921.CQOukoFCf9@thomas \
    --to=thomas@monjalon.net \
    --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=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 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.