From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <thomas@monjalon.net> Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by dpdk.org (Postfix) with ESMTP id 389B258C4; Wed, 12 Dec 2018 11:17:40 +0100 (CET) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id C1DAC21EF6; Wed, 12 Dec 2018 05:17:39 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Wed, 12 Dec 2018 05:17:39 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding:content-type; s=mesmtp; bh=Qz5V72vnWX8QmlAw0GRggDfTJp2EdtQvNLxDu+qFoOI=; b=apizYeViBSYF gZfBqLUA9YqHKAGMvnboAmBfgDRhwtIjLpQ+uZz6Ss4NJx+PwatvCCNt0rARU3uG A9I37p71AA0uZTiMNpfqt4UOvWgXD5lskbjLf5Pd8OzZQCoxGZQHZQLSIFR4FnHy sIkNIn2DD63TP8/PglYVAabhLVC0b0o= 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-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=Qz5V72vnWX8QmlAw0GRggDfTJp2EdtQvNLxDu+qFo OI=; b=ASwiL1liRhOXFy0fZNHQnq5ZlPMEmsFYJUYjCO2D9LVqIW8aMoTHl2hYz eDJ19tPftbhVrgxrgPf0B74q4CrVut/TCggVErJRi6yW8EZ9jxqEFPnsXoT8CwgZ wkABwRDDr9AD2tODhLkJkkInHeUWKGYoo/RQCuiwr+cwGwMaNPbt6FwIJ0W1Ryr4 vYtBSwTh6bGGCHKzBUXZPEdn+4QzmgyEEOqg5IqI4cmjX+yTuGonuzojVwXcfZmQ buy6XNfdwvn/MCNDaFEe1IGdTwuVqtpmIqqvUaRn+tYNQ9jRDkWAwWf+1vzJDlq5 jYlZXRiEqP+laZyBoMC99dHnNyXLQ== X-ME-Sender: <xms:QuAQXFO3tHfb4qdwkg8H47LRieKlJEAdOULrkLNB5ca_oKNqb1iw4w> X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedtkedrudegledgudduucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfquhhtnecuuegrihhlohhuthemucef tddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenucfjughrpefhvffufffkjg hfggfgtgesthfuredttddtvdenucfhrhhomhepvfhhohhmrghsucfoohhnjhgrlhhonhcu oehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtqeenucffohhmrghinhepughpughkrd horhhgnecukfhppeejjedrudefgedrvddtfedrudekgeenucfrrghrrghmpehmrghilhhf rhhomhepthhhohhmrghssehmohhnjhgrlhhonhdrnhgvthenucevlhhushhtvghrufhiii gvpedt X-ME-Proxy: <xmx:QuAQXOEiXokWgEa-n6lJ-SQH2peVtYeLAVEf0C2Sxfg1cFXn80G3vg> <xmx:QuAQXIgJiKXkd_QE0fVuGfXl7x22RjjOKhreA2Xt6xxvUpnuNTA4dg> <xmx:QuAQXCQgimqPDhrUldTXmHfrrsxNLJ1kaqb8ozM_SZZVgrDLGp7IDQ> <xmx:QuAQXI9aA4z2-uTSc9GRqSViXAp8ETDVLaYBgwU_SYWnX_6R4Fd2Tw> <xmx:QuAQXATzWANZjSVWNycR9R1w5sJR_02izozI_NHEfgO12HVnC-CeAg> <xmx:Q-AQXNOg4my-clHfI-BJxtID6qPJLiQc10ODnYxi_PgfnbulITa3Qg> Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id 86057E4445; Wed, 12 Dec 2018 05:17:37 -0500 (EST) From: Thomas Monjalon <thomas@monjalon.net> To: Yasufumi Ogawa <ogawa.yasufumi@lab.ntt.co.jp> Cc: Ferruh Yigit <ferruh.yigit@intel.com>, dpdk-web <web@dpdk.org>, dpdk-spp <spp@dpdk.org> Date: Wed, 12 Dec 2018 11:17:32 +0100 Message-ID: <1704380.LblYpThBnZ@xps> In-Reply-To: <54858905-3c47-2636-080a-55799c18e2cf@lab.ntt.co.jp> References: <db7a445d-a425-dff7-f7db-f92940b4bf3f@intel.com> <2655191.rBOfXtWzeA@xps> <54858905-3c47-2636-080a-55799c18e2cf@lab.ntt.co.jp> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" 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 <web.dpdk.org> List-Unsubscribe: <https://mails.dpdk.org/options/web>, <mailto:web-request@dpdk.org?subject=unsubscribe> List-Archive: <http://mails.dpdk.org/archives/web/> List-Post: <mailto:web@dpdk.org> List-Help: <mailto:web-request@dpdk.org?subject=help> List-Subscribe: <https://mails.dpdk.org/listinfo/web>, <mailto:web-request@dpdk.org?subject=subscribe> X-List-Received-Date: Wed, 12 Dec 2018 10:17:40 -0000 12/12/2018 07:22, Yasufumi Ogawa: > > 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. I use python3 but the server dpdk.org uses python2. > > 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 This does not trigger compilation of the doc. You must use *annotated* tags. > Thanks, > Yasufumi > > > > I fixed all above 3 issues, sent the patch, and updated the doc on dpdk.org.