From: =?gb18030?B?s8no69XfsfA=?= <373755701@qq.com>
To: =?gb18030?B?dXNlcnM=?= <users@dpdk.org>
Subject: [dpdk-users] My questions and Suggestions about the stable DPDK version number
Date: Sat, 10 Dec 2016 10:43:49 +0800 [thread overview]
Message-ID: <tencent_5FAE6A294B0D13547A1049CD@qq.com> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="gb18030", Size: 467 bytes --]
Hi all:
Anyone can tell me why does the DPDK version number dpdk-stable-16.07.1 change to dpdk-stable-16.07.2 and what about the difference between them?
In my opinion, A software's stability begins from its version name. As users, we is sensitive to the version number dpdk-stable-16.07.1.
"dpdk-stable-16.07.1" has been applied to our production environment, but it cannot be found from DPDK website now .
Any help would be appreciated.
next reply other threads:[~2016-12-10 2:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-10 2:43 =?gb18030?B?s8no69XfsfA=?= [this message]
2016-12-10 11:01 ` 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=tencent_5FAE6A294B0D13547A1049CD@qq.com \
--to=373755701@qq.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).