From: Christian Ehrhardt <christian.ehrhardt@canonical.com>
To: "Mcnamara, John" <john.mcnamara@intel.com>
Cc: "stable@dpdk.org" <stable@dpdk.org>,
"Liu, Yuanhan" <yuanhan.liu@intel.com>,
Thomas Monjalon <thomas.monjalon@6wind.com>
Subject: Re: [dpdk-stable] Release note for the stable/lts releases
Date: Thu, 29 Sep 2016 19:29:58 +0200 [thread overview]
Message-ID: <CAATJJ0KLqcr=RBRipNRetxisEhMZqSTYdA9S7Sw9C=PzO=ffDw@mail.gmail.com> (raw)
In-Reply-To: <B27915DBBA3421428155699D51E4CFE202625BDF@IRSMSX103.ger.corp.intel.com>
On Thu, Sep 29, 2016 at 6:39 PM, Mcnamara, John <john.mcnamara@intel.com>
wrote:
> Does that seem okay to everyone?
Seems ok to me at least :-)
Out of backport experience sometimes it is almost more interesting to cover
which ones where not applied and a one liner why.
So if some patch made it to qualify to be looked at, but then be rejected
it would be great to show up in a list:
The following fixes were NOT applied in DPDK 16.07.01 Stable Release:
* examples: fix very-very-unusual-interpreter; Reason: too unusual to
happen
Also I'd pretty much like to get a commit id of the original patch in that
list, so
* kni: fix crash when removing interface
would be
* [5544a453] kni: fix crash when removing interface
What about these suggestions?
--
Christian Ehrhardt
Software Engineer, Ubuntu Server
Canonical Ltd
next prev parent reply other threads:[~2016-09-29 17:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-29 16:39 Mcnamara, John
2016-09-29 17:29 ` Christian Ehrhardt [this message]
2016-10-10 7:52 ` Yuanhan Liu
2016-10-10 8:27 ` Christian Ehrhardt
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='CAATJJ0KLqcr=RBRipNRetxisEhMZqSTYdA9S7Sw9C=PzO=ffDw@mail.gmail.com' \
--to=christian.ehrhardt@canonical.com \
--cc=john.mcnamara@intel.com \
--cc=stable@dpdk.org \
--cc=thomas.monjalon@6wind.com \
--cc=yuanhan.liu@intel.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).