From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) by dpdk.org (Postfix) with ESMTP id DCE842BD2; Thu, 26 Apr 2018 23:02:38 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 49F5E21AAA; Thu, 26 Apr 2018 17:02:38 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Thu, 26 Apr 2018 17:02:38 -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=5IdxRPGX5gEiLMvXkFjji/pGUp sswfZpp9e+bXplb80=; b=BgAr0lX6DaCUVZoezwkgDzfl9Y4rGtSJzji0GeV2g2 CkqB0p3k34qwFvbv7B7lM32urDl/U+fcmH+ULJJOHYClQkqa6ugXHTqnhDKGTEES X/HqEPX9vTjzLlfuOx/BToNkPH4sw4d0T8t7lRoZc43S7QRAWxdrXkwj/QpaPInJ I= 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=fm2; bh=5IdxRP GX5gEiLMvXkFjji/pGUpsswfZpp9e+bXplb80=; b=ElBd3lP6zTGoSj6jDqzT9y euG3DdmJA0hKuh6b0JKgHJNPf5BkvEHz0T80g4V2qEcpnDHCxTc1lW8gexXTBA2B jZ0lLzPr1pEjeD9O31yzvGK/QmTR9q/pLFmoxoQHj1GoK4Ul0f02jv5b+pnTMOHm EBGuq1/RcaFVn9WkPg2vkI0osC3K8XogP8styLcvageZLHgziVCB7Y84wzasyprM t3L86aY16fLpT8Ovi9A6wH51INQ1W6fu/rgxvd4+63Kil5khbyLni4/De5bO6j1x eNCnT8QYUoe4GYvB9gac7ybEz3X3ciTDF8E4eRTAiPs5Lmnv63tk7nNXhz0syesQ == 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 6A47DE47D1; Thu, 26 Apr 2018 17:02:37 -0400 (EDT) From: Thomas Monjalon To: Andrii Cc: Ferruh Yigit , dev@dpdk.org, "Van Haaren, Harry" , marketing@dpdk.org Date: Thu, 26 Apr 2018 23:02:35 +0200 Message-ID: <1998816.mGgKehPjpq@xps> In-Reply-To: References: <2051185.1oe58NAx7W@xps> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] how can I get a git version of Latest Major release? (18.02.1) X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Apr 2018 21:02:39 -0000 I've sent a patch to fix the link in the download page http://dpdk.org/rel http://dpdk.org/ml/archives/web/2018-April/000698.html 26/04/2018 21:25, Andrii: > when its not clear how to get a stable release from git - it sucks. > I don't care which part of team it is: web, dev or marketing. > now there should be one more stupid joke about broken link. > > On Thu, Apr 26, 2018 at 7:27 PM, Thomas Monjalon > wrote: > > > 26/04/2018 18:15, Ferruh Yigit: > > > On 4/26/2018 4:58 PM, Thomas Monjalon wrote: > > > > 25/04/2018 19:23, Andrii: > > > >> The problem here is that common dpdk user is not able to find a stable > > > >> repository > > > >> from a website. > > > >> That would be great if dpdk.com/download or dpdk.com/dev would > > contain > > > >> a direct link to http://dpdk.org/browse/ for example. > > > > > > > > It is already like that. Check the first link of http://dpdk.com/dev > > > > > > just in case to not confuse anyone :) https://dpdk.org/dev > > > > Oh! So it's right, there is not link to git from dpdk.com/dev ;) > > > > Andrii, I think your point is about improving the website experience, > > with a better wording perhaps. > > Please be aware that it is a work in progress by the marketing group > > with the Linux Foundation. They will share some big improvements soon.