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 16D2E2B92 for ; Wed, 29 Aug 2018 00:16:33 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 9285321BA9; Tue, 28 Aug 2018 18:16:32 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Tue, 28 Aug 2018 18:16:32 -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=DyUPXxjxNV7M8qzsKeQJOVNHMx 9iqmXNp1NWpRalXYw=; b=lOgjzwtbhn8Z4E6mFR9GgvDFHX69X5XyEnKtVDGfO6 BePsZ2dHKIhk4DxitDk6QAoap9G6qdom/tFz6jzdZfR8As4cB729JbrXVrnxNyDt NSxGwJXwMzdiMuZAqUETptcQfYaoRR3YADXDDINoR4yXlNdMVPB2fNmA/XOI5XAB g= 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=DyUPXx jxNV7M8qzsKeQJOVNHMx9iqmXNp1NWpRalXYw=; b=P1RITmQIiCkmc2dnGfYDWW CfcWKanUg29AqCkIusC0p28NFZDvVE95i8cf7cMQi979QkPOYlwfSBWwqjKIMN+D EGcfxN21d5lxyT/HQS0zKhf43MecE760kqamWXm1F83khQfPaxEhMd3lohSME7h5 xG14CjJwBMWyA5mNGzir2BoM+KGMw8HdzzB8lqPf84Ss6yUYid8bh5tYh46QvINT RYQOjePCtj7lm7HRHJbut0n8Jiqfvl/EpDZBTrRMyEkyCaIeMFv+6Rfwmyr2d88G 2tN2NxZkfdfpc64IwAb/63fmDhzD3olaW0pEzjLuKaFuU6uHddzIxcoUS1u1PdoQ == X-ME-Proxy: X-ME-Sender: Received: from xps.localnet (94.196.136.77.rev.sfr.net [77.136.196.94]) by mail.messagingengine.com (Postfix) with ESMTPA id 2860F10288; Tue, 28 Aug 2018 18:16:30 -0400 (EDT) From: Thomas Monjalon To: Ferruh Yigit Cc: web@dpdk.org Date: Wed, 29 Aug 2018 00:16:29 +0200 Message-ID: <5467076.kHbuGcLDmn@xps> In-Reply-To: <441cbc2b-1f63-a51c-63e3-0a25bbf82915@intel.com> References: <441cbc2b-1f63-a51c-63e3-0a25bbf82915@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-web] Were are the source code of core.dpdk.org located? 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: Tue, 28 Aug 2018 22:16:33 -0000 The new website core.dpdk.org is now hosted in the master branch of dpdk-web.git, replacing the old one. A branch "old" has been created to keep track of the old version. There is a quick start guide in the README file: http://git.dpdk.org/tools/dpdk-web/tree/README I think we need to update the sphinx doc (contributing guide) about the process for updating the website (www and core).