From: Luca Boccassi <bluca@debian.org>
To: dpdk web <web@dpdk.org>
Cc: Thomas Monjalon <thomas@monjalon.net>,
David Marchand <dmarchan@redhat.com>,
Kevin Traynor <ktraynor@redhat.com>,
Christian Ehrhardt <christian.ehrhardt@canonical.com>
Subject: Re: [PATCH v2] release 19.11.14
Date: Thu, 15 Dec 2022 15:56:46 +0000 [thread overview]
Message-ID: <CAMw=ZnQZd9T6D1XqKo9whn4xMdvdMc0-ttVY030+rTHT70ZZUQ@mail.gmail.com> (raw)
In-Reply-To: <20221215154518.386024-1-christian.ehrhardt@canonical.com>
On Thu, 15 Dec 2022 at 15:45, <christian.ehrhardt@canonical.com> wrote:
>
> From: Christian Ehrhardt <christian.ehrhardt@canonical.com>
>
> While going EOL I've mentioned a few times that we might want to
> consider still doing security releases for 19.11.x in the future.
> Hence I left my name as maintainer so you know who to bother doing
> so.
>
> Signed-off-by: Christian Ehrhardt <christian.ehrhardt@canonical.com>
> ---
> content/download/_index.md | 2 +-
> content/roadmap/_index.md | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
Acked-by: Luca Boccassi <bluca@debian.org>
prev parent reply other threads:[~2022-12-15 15:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-15 15:45 christian.ehrhardt
2022-12-15 15:56 ` Luca Boccassi [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='CAMw=ZnQZd9T6D1XqKo9whn4xMdvdMc0-ttVY030+rTHT70ZZUQ@mail.gmail.com' \
--to=bluca@debian.org \
--cc=christian.ehrhardt@canonical.com \
--cc=dmarchan@redhat.com \
--cc=ktraynor@redhat.com \
--cc=thomas@monjalon.net \
--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).