DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Mcnamara, John" <john.mcnamara@intel.com>
To: "Yigit, Ferruh" <ferruh.yigit@intel.com>,
	"Kovacevic, Marko" <marko.kovacevic@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
	Thomas Monjalon <thomas@monjalon.net>,
	Maxime Coquelin <maxime.coquelin@redhat.com>
Subject: Re: [dpdk-dev] [PATCH 1/2] doc/security: clarify pre-release end of the embargo date
Date: Tue, 30 Jul 2019 11:16:50 +0000	[thread overview]
Message-ID: <B27915DBBA3421428155699D51E4CFE24BCA1BFE@IRSMSX103.ger.corp.intel.com> (raw)
In-Reply-To: <20190617160648.8506-1-ferruh.yigit@intel.com>

> -----Original Message-----
> From: Yigit, Ferruh
> Sent: Monday, June 17, 2019 5:07 PM
> To: Mcnamara, John <john.mcnamara@intel.com>; Kovacevic, Marko
> <marko.kovacevic@intel.com>
> Cc: dev@dpdk.org; Thomas Monjalon <thomas@monjalon.net>; Maxime Coquelin
> <maxime.coquelin@redhat.com>
> Subject: [PATCH 1/2] doc/security: clarify pre-release end of the embargo
> date
> 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>

  parent reply	other threads:[~2019-07-30 11:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-17 16:06 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 ` Mcnamara, John [this message]
2020-05-24 23:04   ` [dpdk-dev] [PATCH 1/2] doc/security: clarify pre-release end of the embargo date Thomas Monjalon

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=B27915DBBA3421428155699D51E4CFE24BCA1BFE@IRSMSX103.ger.corp.intel.com \
    --to=john.mcnamara@intel.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=marko.kovacevic@intel.com \
    --cc=maxime.coquelin@redhat.com \
    --cc=thomas@monjalon.net \


* 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).