From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by dpdk.org (Postfix) with ESMTP id 3914F4CBD for ; Fri, 31 Aug 2018 20:48:03 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 16B4C20F1D; Fri, 31 Aug 2018 14:48:02 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Fri, 31 Aug 2018 14:48:02 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=mesmtp; bh=2d84PrdxIbv4UxXE8ihpIavc7b 1jLTr1j7DQbOrrmgE=; b=mAbC3Rx6Qnbe2v9FbWFteth4viLdWRxT8J3ZWbemNv KQxCYp+9rRyl1XQMs4ZEzcEE7PHPnXVWqNsPcEAH31AzW+ZLuMmRsOFSBQQItBu9 dVenySFaPlap6XdYJ2J1A9UDwmzr3rEsLjALJW2pnpFacYtjTn61ovvkbNuXi9va U= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=2d84Pr dxIbv4UxXE8ihpIavc7b1jLTr1j7DQbOrrmgE=; b=A8y29cygayci8iMS2y070a r+2XO9CjO7JubQKJVzXcNHQTSHrihM2rIHRDlFl8loekXBLuvdJJVQWTPYVST+Q/ /ZXo+hleSx3EEBqsmjn3+R+QJTt03PsrgFk6HwiYLSVjrCyXeqPK0SThuflLVZpA Bvst+lDn0oH5FTYTCITt7TylHrPscXQL9by6QHmGt0+nm+v+aB5a1GRJDWAdlNdz 7YwD85gjZHuBw2vaNPSy3fEnpUl7wMlJTrDAzNrkvfSY2IJO3N/k9K2MBOXU8ly3 h8FUDQZmZ4tg7JBQxjHiDeIbOQqtp5EgkLdP5aUOi54OMD85Nl2XA43iugzRduCg == X-ME-Proxy: X-ME-Sender: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id 970CB10288; Fri, 31 Aug 2018 14:47:59 -0400 (EDT) From: Thomas Monjalon To: Yasufumi Ogawa , Ferruh Yigit Cc: spp@dpdk.org, srv-apl-arch@lab.ntt.co.jp Date: Fri, 31 Aug 2018 20:47:57 +0200 Message-ID: <2257553.aDlJV3Uot4@xps> In-Reply-To: <3145253.k4F035SiiW@xps> References: <5fa35014-45df-6ad6-cb66-d01b6e698d3b@lab.ntt.co.jp> <8006b50e-efa1-baf7-6474-e26c9403a84c@intel.com> <3145253.k4F035SiiW@xps> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [spp] Proposal for RST documentation support X-BeenThere: spp@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Soft Patch Panel List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Aug 2018 18:48:03 -0000 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/ Note that the version number is not updated in the doc when tagging. You should make it dynamic in conf.py as it is done for DPDK, so you won't forget to update it again ;)