From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: users@dpdk.org, dev@dpdk.org
Cc: michael.j.glynn@intel.com
Subject: Re: [dpdk-dev] DPDK Community Survey - about to close
Date: Tue, 02 Aug 2016 14:45:13 +0200 [thread overview]
Message-ID: <9450082.B1U4CBcoeX@xps13> (raw)
In-Reply-To: <9045369.7RH1LsBG8M@xps13>
Just 2 minutes for DPDK ;)
http://surveymonkey.com/r/DPDK_Community_Survey
2016-08-02 14:39, Thomas Monjalon:
> Hi all,
>
> That's the first time a DPDK survey is published.
> It will help us in our future progress to decide what are the most
> important stuff to work on.
>
> Please do not wait to fill it out. It closes on August 4.
> Thanks for taking 2 minutes now to give your feedback.
> When you will have done your duty, you might peacefully do
> your next task or just enjoy a nice August month :)
>
> Each voice counts! Thanks
>
>
> 2016-07-28 16:45, Glynn, Michael J:
> > Hi all
> >
> > As part of our ongoing efforts to improve DPDK, we'd like to hear
> > your feedback!
> >
> > We have created a number of DPDK-related questions here
> > https://www.surveymonkey.com/r/DPDK_Community_Survey
> > and want to hear your views!!
> >
> > The survey will close at midnight GMT on Thursday August 4th
> >
> > Thanks in advance for your feedback - the more responses we get
> > the more data we have to drive further features, improvements, etc...
> > so please respond!!
> >
> > Regards
> > Mike
>
next prev parent reply other threads:[~2016-08-02 12:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-28 16:45 [dpdk-dev] DPDK Community Survey Glynn, Michael J
2016-08-01 21:08 ` Glynn, Michael J
2016-08-02 12:39 ` [dpdk-dev] [dpdk-announce] DPDK Community Survey - about to close Thomas Monjalon
2016-08-02 12:45 ` Thomas Monjalon [this message]
2016-08-04 10:08 ` [dpdk-dev] FW: " Glynn, Michael J
2016-08-29 17:13 ` Glynn, Michael J
2016-10-10 10:42 ` [dpdk-dev] " Glynn, Michael J
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=9450082.B1U4CBcoeX@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=michael.j.glynn@intel.com \
--cc=users@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).