From: Luca Boccassi <bluca@debian.org>
To: Kevin Traynor <ktraynor@redhat.com>, web@dpdk.org, thomas@monjalon.net
Cc: yskoh@mellanox.com
Subject: Re: [dpdk-web] [PATCH] release 18.08.1
Date: Thu, 04 Apr 2019 09:56:01 +0100 [thread overview]
Message-ID: <0db84826af5e9ca0c9d07b16a59e8906b3bdaa37.camel@debian.org> (raw)
In-Reply-To: <20190402102212.27089-1-ktraynor@redhat.com>
On Tue, 2019-04-02 at 11:22 +0100, Kevin Traynor wrote:
> Signed-off-by: Kevin Traynor <
> ktraynor@redhat.com
> >
> ---
> content/download/_index.md | 2 +-
> content/roadmap/_index.md | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/content/download/_index.md b/content/download/_index.md
> index 1e171ac..59a3304 100644
> --- a/content/download/_index.md
> +++ b/content/download/_index.md
> @@ -28,5 +28,5 @@ weight = "2"
> | [DPDK 19.02.0](//fast.dpdk.org/rel/dpdk-19.02.tar.xz) |
> [2019 February 1](//doc.dpdk.org/guides-
> 19.02/rel_notes/release_19_02.html) |
> 23944a2cdee061aa4bd72ebe7d836db0 |
> | [DPDK 18.11.0 (LTS)](//fast.dpdk.org/rel/dpdk-18.11.tar.xz) |
> [2018 November 26](//doc.dpdk.org/guides-
> 18.11/rel_notes/release_18_11.html) |
> 04b86f4a77f4f81a7fbd26467dd2ea9f |
> -| [DPDK 18.08](//fast.dpdk.org/rel/dpdk-18.08.tar.xz) |
> [2018 August 9](//doc.dpdk.org/guides-
> 18.08/rel_notes/release_18_08.html) |
> da5e7fb25ab063c47e53929fb8c58be5 |
> +| [DPDK 18.08.1](//fast.dpdk.org/rel/dpdk-18.08.1.tar.xz) |
> [2019 April 1](//doc.dpdk.org/guides-
> 18.08/rel_notes/release_18_08.html) |
> 391116ff3012ffd33bb63ed5feb3375c |
> | [DPDK 18.05.1](//fast.dpdk.org/rel/dpdk-18.05.1.tar.xz) |
> [2018 Sept 7](//doc.dpdk.org/guides-
> 18.05/rel_notes/release_18_05.html) |
> 5e278012506c76d981e4283a92adec1c |
> | [DPDK 18.02.2](//fast.dpdk.org/rel/dpdk-18.02.2.tar.xz) |
> [2018 June 15](//doc.dpdk.org/guides-
> 18.02/rel_notes/release_18_02.html) |
> 75ad6d39b513649744e49c9fcbbb9ca5 |
> diff --git a/content/roadmap/_index.md b/content/roadmap/_index.md
> index f71927c..49e0976 100644
> --- a/content/roadmap/_index.md
> +++ b/content/roadmap/_index.md
> @@ -110,5 +110,5 @@ by 1-2 weeks, depending on the test results.
> | 18.02.2 | - | - | June 2018 |
> Luca Boccassi |
> | 18.05.1 | - | - | August 2018 |
> Christian Ehrhardt |
> -| - | 18.08.1 | November 16, 2018 | November 2018 |
> Kevin Traynor |
> +| 18.08.1 | - | - | April 2019 |
> Kevin Traynor |
> | - | 18.11.1 | February 15, 2019 | November 2020 (LTS) |
> Kevin Traynor |
> | - | 19.02.1 | May 31, 2019 | June 2019 |
> ? |
>
Acked-by: Luca Boccassi <bluca@debian.org>
--
Kind regards,
Luca Boccassi
next prev parent reply other threads:[~2019-04-04 8:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-02 10:22 Kevin Traynor
2019-04-04 8:55 ` Ferruh Yigit
2019-04-04 8:56 ` Luca Boccassi [this message]
2019-04-08 18:26 ` [dpdk-web] [PATCH 1/2] " Kevin Traynor
2019-04-08 18:26 ` [dpdk-web] [PATCH 2/2] release 18.11.1 Kevin Traynor
2019-04-08 20:00 ` [dpdk-web] [PATCH 1/2] release 18.08.1 Thomas Monjalon
2019-04-09 8:39 ` Kevin Traynor
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=0db84826af5e9ca0c9d07b16a59e8906b3bdaa37.camel@debian.org \
--to=bluca@debian.org \
--cc=ktraynor@redhat.com \
--cc=thomas@monjalon.net \
--cc=web@dpdk.org \
--cc=yskoh@mellanox.com \
/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).