From: "Mcnamara, John" <john.mcnamara@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>, "web@dpdk.org" <web@dpdk.org>
Subject: RE: [PATCH] update 24.03 schedule
Date: Fri, 1 Mar 2024 15:01:13 +0000 [thread overview]
Message-ID: <PH8PR11MB6804B5FB326BF51FA5A15683FC5E2@PH8PR11MB6804.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20240229102123.1367737-1-thomas@monjalon.net>
> -----Original Message-----
> From: Thomas Monjalon <thomas@monjalon.net>
> Sent: Thursday, February 29, 2024 10:21 AM
> To: web@dpdk.org
> Subject: [PATCH] update 24.03 schedule
>
> As discussed in the maintainers meeting, reflect what were the real dates
> of past deadlines, give one more week for -rc2 and adjust other dates:
> http://mails.dpdk.org/archives/dev/2024-February/287767.html
Acked-by: John McNamara <john.mcnamara@intel.com>
next prev parent reply other threads:[~2024-03-01 15:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-29 10:21 Thomas Monjalon
2024-03-01 15:01 ` Mcnamara, John [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-06 21:33 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=PH8PR11MB6804B5FB326BF51FA5A15683FC5E2@PH8PR11MB6804.namprd11.prod.outlook.com \
--to=john.mcnamara@intel.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).