From: Christian Ehrhardt <christian.ehrhardt@canonical.com>
To: Yuanhan Liu <yuanhan.liu@linux.intel.com>
Cc: "Mcnamara, John" <john.mcnamara@intel.com>,
"stable@dpdk.org" <stable@dpdk.org>,
Thomas Monjalon <thomas.monjalon@6wind.com>
Subject: Re: [dpdk-stable] Release note for the stable/lts releases
Date: Mon, 10 Oct 2016 10:27:18 +0200 [thread overview]
Message-ID: <CAATJJ0+=h75WhxsUsOmOpso1Su9GNpCSEH6paZ=VwyrKr_57GA@mail.gmail.com> (raw)
In-Reply-To: <20161010075229.GJ10323@yliu-dev.sh.intel.com>
On Mon, Oct 10, 2016 at 9:52 AM, Yuanhan Liu <yuanhan.liu@linux.intel.com>
wrote:
>
> Hmm, is it an example to show rejected patches only? Or, do you actually
> mean we should not apply it to stable branch? If so, I'm just wondering
> why haven't you stated that while I sent out for comments before.
>
No objection to the patch implied - as you assumed this was only meant to
be an example.
>
> > 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?
>
> Does that matter? I mean, why we should put it in the release note?
>
You are right no need in the release notes.
> OTOH, I have included the original commit info while cherry-pick it from
> upstream. For example,
I like how you included the original commit info - that provides what I
wanted to see - thanks!
--
Christian Ehrhardt
Software Engineer, Ubuntu Server
Canonical Ltd
prev parent reply other threads:[~2016-10-10 8:27 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
2016-10-10 7:52 ` Yuanhan Liu
2016-10-10 8:27 ` Christian Ehrhardt [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='CAATJJ0+=h75WhxsUsOmOpso1Su9GNpCSEH6paZ=VwyrKr_57GA@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@linux.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).