From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>,
Yasufumi Ogawa <ogawa.yasufumi@lab.ntt.co.jp>
Cc: spp@dpdk.org, srv-apl-arch@lab.ntt.co.jp
Subject: Re: [spp] Proposal for RST documentation support
Date: Tue, 4 Sep 2018 12:53:21 +0100 [thread overview]
Message-ID: <c4afeb1c-43a4-be3e-c0a8-bd98729ee87c@intel.com> (raw)
In-Reply-To: <32042811-5338-622c-f99a-4b42ec8f5242@intel.com>
On 9/4/2018 12:51 PM, Ferruh Yigit wrote:
> On 8/31/2018 7:47 PM, Thomas Monjalon wrote:
>> 01/02/2018 14:10, Thomas Monjalon:
>>> 01/02/2018 13:50, Ferruh Yigit:
>>>>> If it is accpted, I would like to propose DPDK community to add a link
>>>>> to https://dpdk.org/doc as similar as pktgen-dpdk, or hosting it on
>>>>> dpdk.org.
>>>>
>>>> And I think this is good idea, cc'ed Thomas for comment.
>>>
>>> Yes we can host it on dpdk.org and automate the generation at each tag.
>>
>> The SPP doc is now hosted on dpdk.org.
>> It is generated whenever a tag is pushed:
>> http://doc.dpdk.org/spp/
>> All versions are available:
>> http://doc.dpdk.org/spp-18.02/
>> http://doc.dpdk.org/spp-18.05/
>
> Great! Thanks Thomas.
Is there link from main dpdk.org page to spp docs?
next prev parent reply other threads:[~2018-09-04 11:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-01 4:00 Yasufumi Ogawa
2018-02-01 12:50 ` Ferruh Yigit
2018-02-01 13:10 ` Thomas Monjalon
2018-02-02 9:27 ` [spp] [spp 02114] " Nakamura Hioryuki
[not found] ` <201802020918.w129IBVm024328@ccmail03.silk.ntt-tx.co.jp>
2018-02-02 9:43 ` [spp] [srv-apl-arch:9031] " Yasufumi Ogawa
2018-08-31 18:47 ` [spp] " Thomas Monjalon
2018-09-03 8:46 ` Yasufumi Ogawa
2018-09-04 11:51 ` Ferruh Yigit
2018-09-04 11:53 ` Ferruh Yigit [this message]
2018-09-04 12:49 ` 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=c4afeb1c-43a4-be3e-c0a8-bd98729ee87c@intel.com \
--to=ferruh.yigit@intel.com \
--cc=ogawa.yasufumi@lab.ntt.co.jp \
--cc=spp@dpdk.org \
--cc=srv-apl-arch@lab.ntt.co.jp \
--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).