From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Neil Horman <nhorman@tuxdriver.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] Next Community Call, Tuesday 2nd December, 8:00 AM GMT
Date: Thu, 04 Dec 2014 12:36:42 +0100 [thread overview]
Message-ID: <3645066.94x2Xsqhy6@xps13> (raw)
In-Reply-To: <20141204113054.GA16249@hmsreliant.think-freely.org>
2014-12-04 06:30, Neil Horman:
> On Wed, Dec 03, 2014 at 11:07:10PM +0000, O'driscoll, Tim wrote:
> > Hi Olga,
> >
> > > Can you please send the presentations from last Community Call.
> > > We have Tetsuya's presentation, if we can also get other presentations it will
> > > be great
> >
> > No problem. Changchun's slides on the converged Virtio driver and Marvin's slides on the DPDK Test Suite are attached.
> >
> Instead of sending this out over email, it might be nice if you archived it on
> dpdk.org. Then people wouldn't have to grep the email server in 6 months if
> they wanted to find these things again
These documents are about developments in progress. The only difference with
other discussions or RFC is that the format is PDF. So I think the mailing list
archives are the right place for it.
Or maybe you are thinking we should have a web page to describe features and attach
such PDF?
--
Thomas
next prev parent reply other threads:[~2014-12-04 11:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-21 16:08 O'driscoll, Tim
2014-11-21 20:21 ` Neil Horman
2014-11-22 10:16 ` Butler, Siobhan A
2014-12-01 2:49 ` Tetsuya Mukawa
2014-12-01 8:35 ` Alex Markuze
2014-12-01 9:51 ` O'driscoll, Tim
2014-12-01 9:40 ` O'driscoll, Tim
2014-12-01 18:33 ` [dpdk-dev] attachment policy Thomas Monjalon
2014-12-02 2:41 ` [dpdk-dev] Next Community Call, Tuesday 2nd December, 8:00 AM GMT Tetsuya Mukawa
2014-12-03 14:55 ` Olga Shern
2014-12-03 23:07 ` O'driscoll, Tim
2014-12-04 11:30 ` Neil Horman
2014-12-04 11:36 ` Thomas Monjalon [this message]
2014-12-04 18:02 ` Neil Horman
2014-12-03 10:48 ` O'driscoll, Tim
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=3645066.94x2Xsqhy6@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=nhorman@tuxdriver.com \
/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).