From: Thomas Monjalon <thomas@monjalon.net>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: marko.kovacevic@intel.com, web@dpdk.org
Subject: Re: [dpdk-web] [PATCH v4] update Intel roadmap for 18.11
Date: Wed, 12 Sep 2018 18:20:43 +0200 [thread overview]
Message-ID: <6741340.EJca0k8ij8@xps> (raw)
In-Reply-To: <85f82c4e-374b-0f04-09aa-086f1267913b@intel.com>
12/09/2018 17:10, Ferruh Yigit:
> On 9/12/2018 1:41 PM, Thomas Monjalon wrote:
> > From: Marko Kovacevic <marko.kovacevic@intel.com>
> >
> > The NAT support was already integrated in DPDK 18.08.
> > The new features were announced in the dpdk-dev mailing list:
> > http://mails.dpdk.org/archives/dev/2018-August/109986.html
> >
> > Signed-off-by: Marko Kovacevic <marko.kovacevic@intel.com>
> > Acked-by: Thomas Monjalon <thomas@monjalon.net>
>
> Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com>
>
> > v4: I have removed most of the upper-casing and words "add" and
> > "support", in order to make it shorter.
> > The items are also moved in order to keep the same kind of sorting
> > we use in the releases notes (EAL, ethdev, crypto, other libs, apps).
>
> Those were copy-paste from Intel Roadmap mail, changing them adds confusion
> about if they are same thing in Roadmap item or not and slows down the updates.
Which change are you referring as adding confusion?
- lowercase?
- remove some verbs?
- sorting list?
> I would prefer original ones but both are OK.
next prev parent reply other threads:[~2018-09-12 16:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-11 15:44 [dpdk-web] [PATCH v2] update " Marko Kovacevic
2018-09-11 16:06 ` Ferruh Yigit
2018-09-11 17:53 ` Thomas Monjalon
2018-09-12 10:59 ` [dpdk-web] [PATCH v3] " Marko Kovacevic
2018-09-12 12:41 ` [dpdk-web] [PATCH v4] update Intel " Thomas Monjalon
2018-09-12 15:10 ` Ferruh Yigit
2018-09-12 16:20 ` Thomas Monjalon [this message]
2018-09-12 16:47 ` Ferruh Yigit
2018-10-16 9:18 ` 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=6741340.EJca0k8ij8@xps \
--to=thomas@monjalon.net \
--cc=ferruh.yigit@intel.com \
--cc=marko.kovacevic@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).