From: Olivier Matz <olivier.matz@6wind.com>
To: dev@dpdk.org
Subject: Re: [dpdk-dev] next technical board meeting, 2017-03-01
Date: Tue, 28 Feb 2017 08:43:42 +0100 [thread overview]
Message-ID: <20170228084342.26d711c7@platinum> (raw)
In-Reply-To: <20170221141115.664e1703@glumotte.dev.6wind.com>
Hello,
Just a reminder for those who want to assist.
Olivier
On Tue, 21 Feb 2017 14:11:15 +0100, Olivier MATZ
<olivier.matz@dev.6wind.com> wrote:
> Hello everyone,
>
> A meeting of the DPDK technical board will occur next week, on
> the 1st of March 2017 at 3pm UTC (4pm France, 11pm PRC, 7am US
> Pacific). The meeting takes place on the #dpdk-board channel on IRC
> (freenode).
>
> This meeting is public, so anybody can join. Only topics on the agenda
> will be discussed. If you want something to be discussed, you can send
> an email to techboard@dpdk.org by February 26th at the latest.
>
> The updated agenda is available here:
> https://bimestriel.framapad.org/p/r.a5199d22813a5ac79d1d365b9cecb905
>
> Olivier
next prev parent reply other threads:[~2017-02-28 7:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-21 13:11 Olivier MATZ
2017-02-28 7:43 ` Olivier Matz [this message]
2017-03-01 11:45 ` 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:
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=20170228084342.26d711c7@platinum \
--to=olivier.matz@6wind.com \
--cc=dev@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 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).