From: Thomas Monjalon <thomas@monjalon.net>
To: luca.boccassi@gmail.com
Cc: web@dpdk.org, Luca Boccassi <bluca@debian.org>
Subject: Re: [dpdk-web] [PATCH] Stable releases 16.11.6, 17.08.2, 17.11.2, 18.02.1
Date: Mon, 23 Apr 2018 16:21:05 +0200 [thread overview]
Message-ID: <304899398.0Cy3JZz3Ny@xps> (raw)
In-Reply-To: <20180423131309.17509-1-luca.boccassi@gmail.com>
Minor nit: not uppercase at the beginning of titles usually.
23/04/2018 15:13, luca.boccassi@gmail.com:
> From: Luca Boccassi <bluca@debian.org>
Maybe an explanation of the reason of this group update?
> Signed-off-by: Luca Boccassi <bluca@debian.org>
> ---
> rel.html | 24 ++++++++++++------------
> 1 file changed, 12 insertions(+), 12 deletions(-)
You need to update the latest stable in download.html.
> --- a/rel.html
> +++ b/rel.html
> - <td><a href="https://fast.dpdk.org/rel/dpdk-18.02.tar.xz">DPDK 18.02</a></td>
> - <td><a href="/doc/guides/rel_notes/release_18_02.html">2018 February 14</a></td>
> - <td><pre>ca13077a014a2102c6e10153dfa3b920</pre></td>
> + <td><a href="https://fast.dpdk.org/rel/dpdk-18.02.1.tar.xz">DPDK 18.02.1</a></td>
> + <td><a href="/doc/guides/rel_notes/release_18_02.html">2018 April 23</a></td>
It should be /guides-18.02/
> + <td><pre>3bbb5468f662e1f7472d4abc5c4cf08e</pre></td>
> </tr>
> <tr>
> - <td><a href="https://fast.dpdk.org/rel/dpdk-17.11.1.tar.xz">DPDK 17.11.1 (LTS)</a></td>
> - <td><a href="/doc/guides-17.11/rel_notes/release_17_11.html">2018 February 27</a></td>
> - <td><pre>a485123bcc242b8248208eb98a8588f2</pre></td>
> + <td><a href="https://fast.dpdk.org/rel/dpdk-17.11.2.tar.xz">DPDK 17.11.2 (LTS)</a></td>
> + <td><a href="/doc/guides-17.11/rel_notes/release_17_11.html">2018 April 23</a></td>
> + <td><pre>e5dba0130c776d898fe0a9e85c28c42b</pre></td>
> </tr>
> <tr>
> - <td><a href="https://fast.dpdk.org/rel/dpdk-17.08.1.tar.xz">DPDK 17.08.1</a></td>
> - <td><a href="/doc/guides-17.08/rel_notes/release_17_08.html">2017 December 7</a></td>
> - <td><pre>faea23aa2899508b1738999d6f12502c</pre></td>
> + <td><a href="https://fast.dpdk.org/rel/dpdk-17.08.2.tar.xz">DPDK 17.08.2</a></td>
> + <td><a href="/doc/guides-17.08/rel_notes/release_17_08.html">2018 April 23</a></td>
> + <td><pre>dd239a878c8c40cf482fdfe438f8d99c</pre></td>
> </tr>
> <tr>
> <td><a href="https://fast.dpdk.org/rel/dpdk-17.05.2.tar.xz">DPDK 17.05.2</a></td>
> @@ -85,9 +85,9 @@
> <td><pre>cbdf8b7a92ce934d47c38cbc9c20c54a</pre></td>
> </tr>
> <tr>
> - <td><a href="https://fast.dpdk.org/rel/dpdk-16.11.5.tar.xz">DPDK 16.11.5 (LTS)</a></td>
> - <td><a href="/doc/guides-16.11/rel_notes/release_16_11.html">2018 March 7</a></td>
> - <td><pre>0fafaca7948ebdd11d7d388b06b21d56</pre></td>
> + <td><a href="https://fast.dpdk.org/rel/dpdk-16.11.6.tar.xz">DPDK 16.11.6 (LTS)</a></td>
> + <td><a href="/doc/guides-16.11/rel_notes/release_16_11.html">2018 April 23</a></td>
> + <td><pre>b5a3fc3d96a3cb8a85325cc24cfe56e7</pre></td>
Checked the tarballs checksums:
b5a3fc3d96a3cb8a85325cc24cfe56e7 dpdk-16.11.6.tar.xz
dd239a878c8c40cf482fdfe438f8d99c dpdk-17.08.2.tar.xz
e5dba0130c776d898fe0a9e85c28c42b dpdk-17.11.2.tar.xz
3bbb5468f662e1f7472d4abc5c4cf08e dpdk-18.02.1.tar.xz
next prev parent reply other threads:[~2018-04-23 14:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-23 13:13 luca.boccassi
2018-04-23 14:21 ` Thomas Monjalon [this message]
2018-04-23 14:34 ` [dpdk-web] [PATCH v2] stable " luca.boccassi
2018-04-23 14:38 ` 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=304899398.0Cy3JZz3Ny@xps \
--to=thomas@monjalon.net \
--cc=bluca@debian.org \
--cc=luca.boccassi@gmail.com \
--cc=web@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).