From: Kevin Traynor <ktraynor@redhat.com>
To: David Marchand <david.marchand@redhat.com>
Cc: web@dpdk.org, bluca@debian.org, thomas@monjalon.net,
christian.ehrhardt@canonical.com, xuemingl@nvidia.com
Subject: Re: [PATCH] release 21.11.5
Date: Thu, 24 Aug 2023 15:00:40 +0100 [thread overview]
Message-ID: <03d132b9-67d6-f6cb-e9f4-067f38b11bff@redhat.com> (raw)
In-Reply-To: <CAJFAV8wkwkcumUCO7ek7cYW6oV+V=jVRPDQt+SoQSC5qQ3_Bew@mail.gmail.com>
On 24/08/2023 14:46, David Marchand wrote:
> On Thu, Aug 24, 2023 at 3:36 PM Kevin Traynor <ktraynor@redhat.com> 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 e2d5d30..c5fa6af 100644
>> --- a/content/download/_index.md
>> +++ b/content/download/_index.md
>> @@ -31,5 +31,5 @@ weight = "2"
>> | [DPDK 22.07.0](//fast.dpdk.org/rel/dpdk-22.07.tar.xz) | [2022 July 17](//doc.dpdk.org/guides-22.07/rel_notes/release_22_07.html) | fb73b58b80b1349cd05fe9cf6984afd4 |
>> | [DPDK 22.03.0](//fast.dpdk.org/rel/dpdk-22.03.tar.xz) | [2022 March 17](//doc.dpdk.org/guides-22.03/rel_notes/release_22_03.html) | a07ca8839f98062f46e1cc359735cce8 |
>> -| [DPDK 21.11.4 (LTS)](//fast.dpdk.org/rel/dpdk-21.11.4.tar.xz) | [2023 May 17](//doc.dpdk.org/guides-21.11/rel_notes/release_21_11.html) | b24201da07d3fd87cacc2aa03586aed3 |
>> +| [DPDK 21.11.5 (LTS)](//fast.dpdk.org/rel/dpdk-21.11.5.tar.xz) | [2023 August 24](//doc.dpdk.org/guides-21.11/rel_notes/release_21_11.html) | fb010eddcd673fcf98782a10cf00b7ae |
>> | [DPDK 21.08.0](//fast.dpdk.org/rel/dpdk-21.08.tar.xz) | [2021 August 8](//doc.dpdk.org/guides-21.08/rel_notes/release_21_08.html) | de33433a1806280996a0ecbe66e3642f |
>> | [DPDK 21.05.0](//fast.dpdk.org/rel/dpdk-21.05.tar.xz) | [2021 May 21](//doc.dpdk.org/guides-21.05/rel_notes/release_21_05.html) | a78bba290b11d9717d1272cc6bfaf7c3 |
>> diff --git a/content/roadmap/_index.md b/content/roadmap/_index.md
>> index 5f501cf..2065a8f 100644
>> --- a/content/roadmap/_index.md
>> +++ b/content/roadmap/_index.md
>> @@ -145,4 +145,4 @@ by 3-6 weeks, depending on the test results.
>> | 19.11.14 | - | - | December 2022 (EOL) | Christian Ehrhardt |
>> | 20.11.9 | 20.11.10 | December 2023 | December 2023 (LTS) | Luca Boccassi |
>> -| 21.11.4 | 21.11.5 | August 2023 | November 2023 (LTS) | Kevin Traynor |
>> +| 21.11.5 | 21.11.6 | December 2023 | December 2023 (LTS) | Kevin Traynor |
>> | 22.11.2 | 22.11.3 | August 2023 | November 2024 (LTS) | Xueming Li |
>> --
>> 2.41.0
>
> Acked-by: David Marchand <david.marchand@redhat.com>
>
>
Thanks David. Pushed to website.
prev parent reply other threads:[~2023-08-24 14:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-24 13:36 Kevin Traynor
2023-08-24 13:46 ` David Marchand
2023-08-24 14:00 ` Kevin Traynor [this message]
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=03d132b9-67d6-f6cb-e9f4-067f38b11bff@redhat.com \
--to=ktraynor@redhat.com \
--cc=bluca@debian.org \
--cc=christian.ehrhardt@canonical.com \
--cc=david.marchand@redhat.com \
--cc=thomas@monjalon.net \
--cc=web@dpdk.org \
--cc=xuemingl@nvidia.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).