From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Yasufumi Ogawa <ogawa.yasufumi@lab.ntt.co.jp>,
spp@dpdk.org, nakamura.hiroyuki@po.ntt-tx.co.jp
Subject: Re: [spp] [PATCH 01/15] docs: add rst docs
Date: Tue, 6 Feb 2018 15:22:03 +0000 [thread overview]
Message-ID: <ba39a31d-b07b-2658-ab48-83bd2598521e@intel.com> (raw)
In-Reply-To: <2e57d878-0f51-967a-d1dd-38e1d02492e8@lab.ntt.co.jp>
On 2/5/2018 2:34 AM, Yasufumi Ogawa wrote:
> Hi, Ferruh
>
> I completed to migrate markdown documents to RST and prepare patches.
> Could you merge this 15 patches, then next patches I will send after
> this mail. This update includes spp_vf documentation sent from Hiroyuki.
Series applied, thanks.
>
> Thanks,
> Yasufumi
>
> On 2018/02/01 13:04, ogawa.yasufumi@lab.ntt.co.jp wrote:
>> From: Yasufumi Ogawa <ogawa.yasufumi@lab.ntt.co.jp>
>>
>> This is the first commit to move markdown documents to rst.
>>
>> Current documents are moved to each of directories of category. Top
>> directory of rst files is 'guides' which contains three category
>> directories, 'commands', 'setup' and 'tools'.
>>
>> docs/guides/
>> ├── commands
>> ├── index.rst
>> ├── overview.rst
>> ├── setup
>> │ ├── index.rst
>> │ └── setup_guide.rst
>> └── tools
>>
>> Signed-off-by: Yasufumi Ogawa <ogawa.yasufumi@lab.ntt.co.jp>
<...>
prev parent reply other threads:[~2018-02-06 15:22 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-01 4:04 ogawa.yasufumi
2018-02-01 4:04 ` [spp] [PATCH 02/15] docs: add overview ogawa.yasufumi
2018-02-01 4:04 ` [spp] [PATCH 03/15] docs: add primary commands ogawa.yasufumi
2018-02-01 4:04 ` [spp] [PATCH 04/15] docs: add common commands ogawa.yasufumi
2018-02-01 4:04 ` [spp] [PATCH 05/15] docs: add secondary commands ogawa.yasufumi
2018-02-01 4:04 ` [spp] [PATCH 06/15] docs: add descriptions for pri commands ogawa.yasufumi
2018-02-01 4:04 ` [spp] [PATCH 07/15] docs: fix erata of help command ogawa.yasufumi
2018-02-01 4:04 ` [spp] [PATCH 08/15] docs: revise index in setup chapter ogawa.yasufumi
2018-02-01 4:04 ` [spp] [PATCH 09/15] docs: update getting_started section ogawa.yasufumi
2018-02-01 4:04 ` [spp] [PATCH 10/15] docs: update howto_use section ogawa.yasufumi
2018-02-01 4:04 ` [spp] [PATCH 11/15] docs: add performance_opt section ogawa.yasufumi
2018-02-01 4:04 ` [spp] [PATCH 12/15] docs: update use_cases section ogawa.yasufumi
2018-02-01 4:04 ` [spp] [PATCH 13/15] docs: update overview section ogawa.yasufumi
2018-02-01 4:05 ` [spp] [PATCH 14/15] docs: add compile script for rst documentation ogawa.yasufumi
2018-02-01 4:05 ` [spp] [PATCH 15/15] makefile: add target for compile rst documents ogawa.yasufumi
2018-02-05 2:34 ` [spp] [PATCH 01/15] docs: add rst docs Yasufumi Ogawa
2018-02-06 15:22 ` Ferruh Yigit [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=ba39a31d-b07b-2658-ab48-83bd2598521e@intel.com \
--to=ferruh.yigit@intel.com \
--cc=nakamura.hiroyuki@po.ntt-tx.co.jp \
--cc=ogawa.yasufumi@lab.ntt.co.jp \
--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).