DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Andrii <bearrailgun@gmail.com>
Cc: Ferruh Yigit <ferruh.yigit@intel.com>,
	dev@dpdk.org, "Van Haaren, Harry" <harry.van.haaren@intel.com>,
	marketing@dpdk.org
Subject: Re: [dpdk-dev] how can I get a git version of Latest Major release? (18.02.1)
Date: Thu, 26 Apr 2018 18:27:05 +0200	[thread overview]
Message-ID: <2051185.1oe58NAx7W@xps> (raw)
In-Reply-To: <624561fa-af4f-ac20-ad25-19224a64e1c5@intel.com>

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.

  reply	other threads:[~2018-04-26 16:27 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-25 13:44 Andrii
2018-04-25 13:47 ` Van Haaren, Harry
2018-04-25 14:02   ` Andrii
2018-04-25 14:45     ` Thomas Monjalon
2018-04-25 14:47     ` Ferruh Yigit
2018-04-25 17:23       ` Andrii
2018-04-26 15:58         ` Thomas Monjalon
2018-04-26 16:15           ` Ferruh Yigit
2018-04-26 16:27             ` Thomas Monjalon [this message]
2018-04-26 19:25               ` Andrii
2018-04-26 21:02                 ` Thomas Monjalon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2051185.1oe58NAx7W@xps \
    --to=thomas@monjalon.net \
    --cc=bearrailgun@gmail.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=harry.van.haaren@intel.com \
    --cc=marketing@dpdk.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).