From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: John McNamara <john.mcnamara@intel.com>
Cc: dev@dpdk.org, Bruce Richardson <bruce.richardson@intel.com>
Subject: Re: [dpdk-dev] [PATCH v2] doc: improve wording of new features section
Date: Thu, 28 Jul 2016 17:25:43 +0200 [thread overview]
Message-ID: <2217509.K73HIC3SYN@xps13> (raw)
In-Reply-To: <1469626015-28689-1-git-send-email-john.mcnamara@intel.com>
2016-07-27 14:26, John McNamara:
> Improve the wording of some text in the "new features" section of
> the release notes.
>
> Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
> Signed-off-by: John McNamara <john.mcnamara@intel.com>
Applied, thanks
prev parent reply other threads:[~2016-07-28 15:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-22 16:06 [dpdk-dev] [PATCH 1/2] doc: fix indentation of new feature in release notes Bruce Richardson
2016-07-22 16:06 ` [dpdk-dev] [PATCH 2/2] doc: improve wording of new features section Bruce Richardson
2016-07-22 16:19 ` Thomas Monjalon
2016-07-25 8:39 ` Bruce Richardson
2016-07-27 13:26 ` [dpdk-dev] [PATCH v2] " John McNamara
2016-07-28 15:25 ` 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=2217509.K73HIC3SYN@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.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).