From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: harry.van.haaren@intel.com
Cc: web@dpdk.org
Subject: Re: [dpdk-web] [PATCH v2] roadmap for 16.07
Date: Mon, 11 Apr 2016 22:10:57 +0200 [thread overview]
Message-ID: <8491664.yDNzZBaRqv@xps13> (raw)
In-Reply-To: <1460405154-9269-1-git-send-email-thomas.monjalon@6wind.com>
2016-04-11 22:05, Thomas Monjalon:
> From: Harry van Haaren <harry.van.haaren@intel.com>
>
> Add roadmap items for 16.07, remove 16.04 from schedule.
>
> Signed-off-by: Harry van Haaren <harry.van.haaren@intel.com>
> Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com>
> ---
> dev/roadmap.html | 67 +++++++++++++++++++++++++++++---------------------------
> 1 file changed, 35 insertions(+), 32 deletions(-)
>
> v2:
> - add more 16.07 topics from mailing list patches
> - add some 16.11 topics from discussions
Applied
prev parent reply other threads:[~2016-04-11 20:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-07 13:30 [dpdk-web] [PATCH] roadmap: update items to 16.07 Harry van Haaren
2016-04-11 20:05 ` [dpdk-web] [PATCH v2] roadmap for 16.07 Thomas Monjalon
2016-04-11 20:10 ` Thomas Monjalon [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=8491664.yDNzZBaRqv@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=harry.van.haaren@intel.com \
--cc=web@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).