All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Mcnamara, John" <john.mcnamara@intel.com>
To: Hemant Agrawal <hemant.agrawal@nxp.com>,
	"dev@dpdk.org" <dev@dpdk.org>,
	"techboard@dpdk.org" <techboard@dpdk.org>
Subject: Re: Minutes of tech-board meeting 2017-04-27
Date: Thu, 4 May 2017 11:36:57 +0000	[thread overview]
Message-ID: <B27915DBBA3421428155699D51E4CFE2332C746B@IRSMSX103.ger.corp.intel.com> (raw)
In-Reply-To: <DB3PR04MB076270425F3C5C8E7C8B649889160@DB3PR04MB0762.eurprd04.prod.outlook.com>



> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Hemant Agrawal
> Sent: Wednesday, May 3, 2017 6:57 AM
> To: dev@dpdk.org; techboard@dpdk.org
> Subject: [dpdk-dev] Minutes of tech-board meeting 2017-04-27
> 
> Hi all,
> 
> Here is the meeting notes for the last DPDK technical board meeting held
> on 2017-04-27.
> 

Hi,

What is the date for the next Tech Board meeting?

John

      reply	other threads:[~2017-05-04 11:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-03  5:57 Minutes of tech-board meeting 2017-04-27 Hemant Agrawal
2017-05-04 11:36 ` Mcnamara, John [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=B27915DBBA3421428155699D51E4CFE2332C746B@IRSMSX103.ger.corp.intel.com \
    --to=john.mcnamara@intel.com \
    --cc=dev@dpdk.org \
    --cc=hemant.agrawal@nxp.com \
    --cc=techboard@dpdk.org \
    /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.