From: "Dorsett, Michal" <Michal.Dorsett@verint.com>
To: "users@dpdk.org" <users@dpdk.org>
Subject: [dpdk-users] DPDK version 16.4
Date: Mon, 30 May 2016 07:24:22 +0000 [thread overview]
Message-ID: <DAC43FCF19B05149A1D1F5E9005F94F8F1795A60@TLVMBX1.verint.corp.verintsystems.com> (raw)
Hi,
Where can I read about the giant leap from version 2.2 to version 16.4 and the reasons for the huge major numbering difference?
Thanks
--
This electronic message may contain proprietary and confidential
information of Verint Systems Inc., its affiliates and/or subsidiaries.
The information is intended to be for the use of the individual(s) or
entity(ies) named above. If you are not the intended recipient (or
authorized to receive this e-mail for the intended recipient), you may not
use, copy, disclose or distribute to anyone this message or any information
contained in this message. If you have received this electronic message in
error, please notify us by replying to this e-mail.
next reply other threads:[~2016-05-30 7:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-30 7:24 Dorsett, Michal [this message]
2016-05-30 10:08 ` Hyun Yoo
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=DAC43FCF19B05149A1D1F5E9005F94F8F1795A60@TLVMBX1.verint.corp.verintsystems.com \
--to=michal.dorsett@verint.com \
--cc=users@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).