From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from tama50.ecl.ntt.co.jp (tama50.ecl.ntt.co.jp [129.60.39.147]) by dpdk.org (Postfix) with ESMTP id 6733A2C54; Wed, 12 Dec 2018 07:25:12 +0100 (CET) Received: from vc2.ecl.ntt.co.jp (vc2.ecl.ntt.co.jp [129.60.86.154]) by tama50.ecl.ntt.co.jp (8.13.8/8.13.8) with ESMTP id wBC6PB6v023639; Wed, 12 Dec 2018 15:25:11 +0900 Received: from vc2.ecl.ntt.co.jp (localhost [127.0.0.1]) by vc2.ecl.ntt.co.jp (Postfix) with ESMTP id 71405638C73; Wed, 12 Dec 2018 15:25:11 +0900 (JST) Received: from jcms-pop21.ecl.ntt.co.jp (jcms-pop21.ecl.ntt.co.jp [129.60.87.134]) by vc2.ecl.ntt.co.jp (Postfix) with ESMTP id 65C6B638BE4; Wed, 12 Dec 2018 15:25:11 +0900 (JST) Received: from [IPv6:::1] (watercress.nslab.ecl.ntt.co.jp [129.60.13.73]) by jcms-pop21.ecl.ntt.co.jp (Postfix) with ESMTPSA id 5FDA7400A71; Wed, 12 Dec 2018 15:25:11 +0900 (JST) References: <2655191.rBOfXtWzeA@xps> From: Yasufumi Ogawa Message-ID: <54858905-3c47-2636-080a-55799c18e2cf@lab.ntt.co.jp> Date: Wed, 12 Dec 2018 15:22:04 +0900 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0 MIME-Version: 1.0 In-Reply-To: <2655191.rBOfXtWzeA@xps> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-CC-Mail-RelayStamp: 1 To: Thomas Monjalon Cc: Ferruh Yigit , dpdk-web , dpdk-spp X-TM-AS-MML: disable X-Mailman-Approved-At: Mon, 17 Dec 2018 11:34:50 +0100 Subject: Re: [dpdk-web] SPP documentation update on dpdk.org X-BeenThere: web@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK website maintenance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Dec 2018 06:25:14 -0000 > Hi, > > 10/12/2018 17:52, Yasufumi Ogawa: >>> Hi Thomas, >>> >>> Yasufumi was asking how to update SPP documentation on dpdk.or >>> (https://doc.dpdk.org/spp/). >>> >>> Is there something triggered automatically when a document patch applied? Or is >>> it needs to be done manually? How can we manage this doc update? >> Hi Ferruh, Thomas, >> >> Thanks Ferruh for your support! I aske Thomas for documentation and he kindly told me how it is updated with his script. It >> might be my fault because of some of compilation errors of documentation. >> >> I have tried to fix the errors and push to it with new version tag. Thomas, Thank you so much for fixing my problems! > > First issue I see is the error number: > in v18.08 it is defined as VERSION := 18.05.1 > > Second issue: > WARNING: The config value `version' has type `bytes', defaults to `str'. > WARNING: The config value `release' has type `bytes', defaults to `str'. > > There is a third issue with the output of the make command: > make: Entering directory '...' > 18.08 > make: Leaving directory '...' I was curious `make showversion` because make command told me that `-r` is illegal even if giving options same as DPDK and no warnings for compiling DPDK's documentation. By the way, do you use python3 for sphinx-build? I am using python2 and there are no warnings in the second issue while docs compilation. If so, I should update to python3 to be the same environment as yours. > > Last but not the least, the doc will be generated only when you push an annotated tag: > git tag -am spp-18.08 v18.08 I understand pushing tag is also incorrect. I simply added the tag and pushed. $ git tag v18.08 $ git push origin v18.08 Thanks, Yasufumi > > I fixed all above 3 issues, sent the patch, and updated the doc on dpdk.org.