From: "Mcnamara, John" <john.mcnamara@intel.com>
To: Kevin Traynor <ktraynor@redhat.com>, "web@dpdk.org" <web@dpdk.org>
Cc: "bluca@debian.org" <bluca@debian.org>,
"christian.ehrhardt@canonical.com"
<christian.ehrhardt@canonical.com>,
"xuemingl@nvidia.com" <xuemingl@nvidia.com>,
"thomas@monjalon.net" <thomas@monjalon.net>,
"Yigit, Ferruh" <ferruh.yigit@intel.com>,
"david.marchand@redhat.com" <david.marchand@redhat.com>
Subject: RE: [PATCH v2 2/2] add 21.11 LTS roadmap
Date: Thu, 13 Jan 2022 11:17:41 +0000 [thread overview]
Message-ID: <DM6PR11MB322791C2293B916CE340CCBCFC539@DM6PR11MB3227.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20220113101156.189859-2-ktraynor@redhat.com>
> -----Original Message-----
> From: Kevin Traynor <ktraynor@redhat.com>
> Sent: Thursday, January 13, 2022 10:12 AM
> To: web@dpdk.org
> Cc: bluca@debian.org; christian.ehrhardt@canonical.com;
> xuemingl@nvidia.com; thomas@monjalon.net; Yigit, Ferruh
> <ferruh.yigit@intel.com>; david.marchand@redhat.com; Kevin Traynor
> <ktraynor@redhat.com>
> Subject: [PATCH v2 2/2] add 21.11 LTS roadmap
>
> Add initial dates and maintainer for 21.11 LTS as approved by Techboard in
> http://mails.dpdk.org/archives/dev/2021-December/230920.html
Thanks for stepping up.
Acked-by: John McNamara <john.mcnamara@intel.com>
next prev parent reply other threads:[~2022-01-13 11:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20211213164858.74244-1-ktraynor@redhat.com>
2022-01-13 10:11 ` [PATCH v2 1/2] add link in stable release section and update typical timeframe Kevin Traynor
2022-01-13 10:11 ` [PATCH v2 2/2] add 21.11 LTS roadmap Kevin Traynor
2022-01-13 11:17 ` Mcnamara, John [this message]
2022-01-13 10:13 ` [PATCH v2 1/2] add link in stable release section and update typical timeframe 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=DM6PR11MB322791C2293B916CE340CCBCFC539@DM6PR11MB3227.namprd11.prod.outlook.com \
--to=john.mcnamara@intel.com \
--cc=bluca@debian.org \
--cc=christian.ehrhardt@canonical.com \
--cc=david.marchand@redhat.com \
--cc=ferruh.yigit@intel.com \
--cc=ktraynor@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).