From: Thomas Monjalon <thomas@monjalon.net>
To: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
Cc: dev@dpdk.org, Harini Ramakrishnan <haramakr@microsoft.com>
Subject: Re: [dpdk-dev] [PATCH v2] update Windows roadmap
Date: Tue, 21 Sep 2021 16:24:49 +0200 [thread overview]
Message-ID: <3353781.G76zDxh4gq@thomas> (raw)
In-Reply-To: <20210910230708.788333-1-dmitry.kozliuk@gmail.com>
11/09/2021 01:07, Dmitry Kozlyuk:
> Add the current status and the actual roadmap, remove completed entries.
> More detailed plan in the mailing list:
> https://mails.dpdk.org/archives/dev/2021-August/217463.html
>
> Signed-off-by: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
> ---
> v2: improve wording, fix typos, remove improbable items (Thomas).
Applied, thanks.
Note: fixed capitalization VMWare -> VMware
prev parent reply other threads:[~2021-09-21 14:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210827002727.113426-1-dmitry.kozliuk@gmail.com>
2021-09-10 23:07 ` Dmitry Kozlyuk
2021-09-21 14:24 ` Thomas Monjalon [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=3353781.G76zDxh4gq@thomas \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=dmitry.kozliuk@gmail.com \
--cc=haramakr@microsoft.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).