From: Thomas Monjalon <thomas@monjalon.net>
To: David Marchand <david.marchand@redhat.com>
Cc: web@dpdk.org
Subject: Re: [PATCH] release 22.11.1
Date: Fri, 02 Dec 2022 10:23:44 +0100 [thread overview]
Message-ID: <5881797.lOV4Wx5bFT@thomas> (raw)
In-Reply-To: <20221202091709.512156-1-david.marchand@redhat.com>
02/12/2022 10:17, David Marchand:
> --- a/content/download/_index.md
> +++ b/content/download/_index.md
> @@ -13,7 +13,7 @@ weight = "2"
> <a class="dwnld-btn" href="https://fast.dpdk.org/rel/dpdk-22.11.tar.xz">
The link should be updated.
> {{< icon name="glyphicon glyphicon-download-alt" size="large" >}}
> Latest Long Term Stable (LTS)\
> - 22.11.0
> + 22.11.1
The "Latest" link should be updated as well to 22.11.1.
In this case, the stable release is the most up-to-date
and we should not use 22.11.0.
next prev parent reply other threads:[~2022-12-02 9:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-02 9:17 David Marchand
2022-12-02 9:23 ` Thomas Monjalon [this message]
2022-12-02 9:25 ` [PATCH v2] " David Marchand
2022-12-02 9:29 ` 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=5881797.lOV4Wx5bFT@thomas \
--to=thomas@monjalon.net \
--cc=david.marchand@redhat.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).