From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Justin Parus <Justin.Parus@microsoft.com>,
"users@dpdk.org" <users@dpdk.org>
Cc: tdelanerolle@linuxfoundation.org, Thomas Monjalon <thomas@monjalon.net>
Subject: Re: [dpdk-users] Suggestion: DPDK "latest" Download Links
Date: Wed, 22 Aug 2018 10:58:22 +0100 [thread overview]
Message-ID: <cffde2c6-53a3-efb1-4d37-56cec2a5b8ae@intel.com> (raw)
In-Reply-To: <SN6PR2101MB1133C3D10FD2EE65F0F0D4B595320@SN6PR2101MB1133.namprd21.prod.outlook.com>
On 8/20/2018 8:03 PM, Justin Parus wrote:
> Hi,
>
> I would like to propose adding DPDK "latest" download links. For example dpdk-latest-major and dpdk-latest-stable, would automatically update and point to the most recent date major and stable releases respectively. This would be useful for our tests as they would always be testing the latest packages automatically.
+1, looks good idea
cc'ed Thomas & Trishan.
>
> Thanks,
> Justin
>
next prev parent reply other threads:[~2018-08-22 9:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-20 19:03 Justin Parus
2018-08-22 9:58 ` Ferruh Yigit [this message]
[not found] ` <10660669.gPjk7PcmS0@xps>
2018-08-23 21:55 ` Madhan Sivakumar
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=cffde2c6-53a3-efb1-4d37-56cec2a5b8ae@intel.com \
--to=ferruh.yigit@intel.com \
--cc=Justin.Parus@microsoft.com \
--cc=tdelanerolle@linuxfoundation.org \
--cc=thomas@monjalon.net \
--cc=users@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).