From: Thomas Monjalon <thomas@monjalon.net>
To: "Yigit, Ferruh" <ferruh.yigit@intel.com>
Cc: "Kovacevic, Marko" <marko.kovacevic@intel.com>,
dev@dpdk.org, Maxime Coquelin <maxime.coquelin@redhat.com>,
"Mcnamara, John" <john.mcnamara@intel.com>
Subject: Re: [dpdk-dev] [PATCH 1/2] doc/security: clarify pre-release end of the embargo date
Date: Mon, 25 May 2020 01:04:00 +0200 [thread overview]
Message-ID: <3349330.oCiqf3LBnv@thomas> (raw)
In-Reply-To: <B27915DBBA3421428155699D51E4CFE24BCA1BFE@IRSMSX103.ger.corp.intel.com>
30/07/2019 13:16, Mcnamara, John:
> From: Yigit, Ferruh
> > Sent: Monday, June 17, 2019 5:07 PM
> >
> > Clarify that a fixed date will be used for end of embargo (public
> > disclosure) date while communicating with downstream stakeholders.
> >
> > Initial document got a review that it gives an impression that
> > communicated embargo date can be a range like 'less than a week' which is
> > not the case. The range applies when defining the end of the embargo date
> > but a fix date will be communicated.
> >
>
> Acked-by: John McNamara <john.mcnamara@intel.com>
I don't know why these old patches were still pending.
Series applied, better late than never :)
prev parent reply other threads:[~2020-05-24 23:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-17 16:06 [dpdk-dev] [PATCH 1/2] doc/security: clarify pre-release end of the embargo date Ferruh Yigit
2019-06-17 16:06 ` [dpdk-dev] [PATCH 2/2] doc/security: clarify experimental API status Ferruh Yigit
2019-07-30 11:16 ` Mcnamara, John
2019-07-30 11:16 ` [dpdk-dev] [PATCH 1/2] doc/security: clarify pre-release end of the embargo date Mcnamara, John
2020-05-24 23:04 ` Thomas Monjalon [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=3349330.oCiqf3LBnv@thomas \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=john.mcnamara@intel.com \
--cc=marko.kovacevic@intel.com \
--cc=maxime.coquelin@redhat.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.