From: "Mcnamara, John" <john.mcnamara@intel.com>
To: "Yigit, Ferruh" <ferruh.yigit@intel.com>,
"Kovacevic, Marko" <marko.kovacevic@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
Thomas Monjalon <thomas@monjalon.net>,
Shreyansh Jain <shreyansh.jain@nxp.com>
Subject: Re: [dpdk-dev] [PATCH v2] doc: add suggested new feature order to release notes
Date: Wed, 6 Jun 2018 09:46:18 +0000 [thread overview]
Message-ID: <B27915DBBA3421428155699D51E4CFE23F361E15@IRSMSX103.ger.corp.intel.com> (raw)
In-Reply-To: <20180605134424.35529-1-ferruh.yigit@intel.com>
> -----Original Message-----
> From: Yigit, Ferruh
> Sent: Tuesday, June 5, 2018 2:44 PM
> To: Mcnamara, John <john.mcnamara@intel.com>; Kovacevic, Marko
> <marko.kovacevic@intel.com>
> Cc: dev@dpdk.org; Yigit, Ferruh <ferruh.yigit@intel.com>; Thomas Monjalon
> <thomas@monjalon.net>; Shreyansh Jain <shreyansh.jain@nxp.com>
> Subject: [PATCH v2] doc: add suggested new feature order to release notes
>
> Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>
> ---
> Cc: Shreyansh Jain <shreyansh.jain@nxp.com>
>
> v2:
> * Wording fixed
> ---
> doc/guides/rel_notes/release_18_08.rst | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/doc/guides/rel_notes/release_18_08.rst
> b/doc/guides/rel_notes/release_18_08.rst
> index 5bc23c537..bce01b550 100644
> --- a/doc/guides/rel_notes/release_18_08.rst
> +++ b/doc/guides/rel_notes/release_18_08.rst
> @@ -37,6 +37,9 @@ New Features
>
> Refer to the previous release notes for examples.
>
> + Suggested order of items in release note:
> + core libs, device abstraction libs and PMDs, other libs, apps,
> examples, unit test
Good idea.
The line should be wrapped or maybe added as a list like this:
* Core libs
* Device abstraction libs and PMDs
* Other libs
* Apps
* Examples
* Unit tests
But that is minor, so.
Acked-by: John McNamara <john.mcnamara@intel.com>
next prev parent reply other threads:[~2018-06-06 9:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-05 9:21 [dpdk-dev] [PATCH] " Ferruh Yigit
2018-06-05 12:36 ` Shreyansh Jain
2018-06-05 13:37 ` Ferruh Yigit
2018-06-05 13:44 ` [dpdk-dev] [PATCH v2] " Ferruh Yigit
2018-06-06 9:46 ` Mcnamara, John [this message]
2018-06-11 12:11 ` [dpdk-dev] [PATCH v3] " Ferruh Yigit
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=B27915DBBA3421428155699D51E4CFE23F361E15@IRSMSX103.ger.corp.intel.com \
--to=john.mcnamara@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=marko.kovacevic@intel.com \
--cc=shreyansh.jain@nxp.com \
--cc=thomas@monjalon.net \
/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).