From: yasufum.o@gmail.com
To: spp@dpdk.org, ferruh.yigit@intel.com, yasufum.o@gmail.com
Subject: [spp] [PATCH 0/2] Revise GSG chapter
Date: Tue, 17 Sep 2019 21:23:17 +0900 [thread overview]
Message-ID: <20190917122319.16129-1-yasufum.o@gmail.com> (raw)
From: Yasufumi Ogawa <yasufum.o@gmail.com>
As CentOS support was added to SPP, documentation was updated to
describe both of installations of Ubuntu and CentOS. However, there are
still some ambiguous descriptions and not clear for which cases, or
remained old descriptions in `Getting Started Guide`. This series of
patches is to revise them.
Yasufumi Ogawa (2):
docs: revise misc in setup section
docs: update install section
docs/guides/gsg/install.rst | 38 ++++++++++++++++++---------------
docs/guides/gsg/setup.rst | 42 ++++++++++++++++++++++---------------
2 files changed, 46 insertions(+), 34 deletions(-)
--
2.17.1
next reply other threads:[~2019-09-17 12:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-17 12:23 yasufum.o [this message]
2019-09-17 12:23 ` [spp] [PATCH 1/2] docs: revise misc in setup section yasufum.o
2019-09-17 12:23 ` [spp] [PATCH 2/2] docs: update install section yasufum.o
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=20190917122319.16129-1-yasufum.o@gmail.com \
--to=yasufum.o@gmail.com \
--cc=ferruh.yigit@intel.com \
--cc=spp@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).