From: Vincent JARDIN <vincent.jardin@6wind.com>
To: Jan Blunck <Jan.Blunck@brocade.com>,
"Matt.Spencer@arm.com" <Matt.Spencer@arm.com>,
"moving@dpdk.org" <moving@dpdk.org>
Subject: Re: [dpdk-moving] description of technical governance
Date: Mon, 31 Oct 2016 20:41:53 +0100 [thread overview]
Message-ID: <c2c98a5a-6c96-5bde-4672-9a6a65fcec5a@6wind.com> (raw)
In-Reply-To: <1477938704.2463.48.camel@brocade.com>
Le 31/10/2016 à 19:31, Jan Blunck a écrit :
> This is a transparent process with low entrance
> boundaries that is proven to work also for other projects than DPDK.
+1
next prev parent reply other threads:[~2016-10-31 19:41 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-25 8:58 [dpdk-moving] [Topics] Francois Ozog
2016-10-25 11:27 ` O'Driscoll, Tim
2016-10-25 14:00 ` [dpdk-moving] description of technical governance Thomas Monjalon
2016-10-26 10:21 ` O'Driscoll, Tim
2016-10-28 9:13 ` O'Driscoll, Tim
2016-10-28 16:52 ` Matt Spencer
2016-10-28 19:22 ` Thomas Monjalon
2016-10-28 22:54 ` Vincent Jardin
2016-10-31 15:20 ` Matt Spencer
2016-10-31 16:07 ` Michael Dolan
2016-10-31 16:18 ` Matt Spencer
2016-10-31 16:33 ` Michael Dolan
2016-10-31 16:43 ` Matt Spencer
2016-10-31 16:52 ` Michael Dolan
2016-10-31 16:56 ` O'Driscoll, Tim
2016-10-31 16:58 ` Michael Dolan
2016-10-31 18:31 ` Jan Blunck
2016-10-31 19:41 ` Vincent JARDIN [this message]
[not found] ` <DB5PR04MB1605482F1C67F9B797EB9AE289A60@DB5PR04MB1605.eurprd04.prod.outlook.com>
2016-11-08 8:11 ` Jaswinder Singh
2016-11-08 9:37 ` O'Driscoll, Tim
2016-12-20 14:41 ` Thomas Monjalon
2016-10-25 14:55 ` [dpdk-moving] [Topics] Dave Neary
2016-10-26 12:47 ` Dave Neary
2016-10-26 15:00 ` Francois Ozog
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=c2c98a5a-6c96-5bde-4672-9a6a65fcec5a@6wind.com \
--to=vincent.jardin@6wind.com \
--cc=Jan.Blunck@brocade.com \
--cc=Matt.Spencer@arm.com \
--cc=moving@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).