From: "Nélio Laranjeiro" <nelio.laranjeiro@6wind.com>
To: stable@dpdk.org, Thomas Monjalon <thomas.monjalon@6wind.com>,
Yuanhan Liu <yuanhan.liu@linux.intel.com>
Subject: [dpdk-stable] What kind of commits can be backported to help the process
Date: Wed, 15 Feb 2017 11:23:45 +0100 [thread overview]
Message-ID: <20170215102345.GU23344@autoinstall.dev.6wind.com> (raw)
Hi stable mailing list,
As written in the subject, it is not fully clear on what kind of patches
can enter this branch.
Some fixes apply easily on top of other ones which may not be related,
the question is on those "unrelated" patches. Is it acceptable to
backport them, and if yes at what point is it acceptable depending on
the nature of the patch:
1. Re-work: just a refactor of some structure, clean-up, ...
2. Behavior: it change the behavior of a part of the code, ...
3. Performances: it impacts performances (positively or negatively).
4. None, the patch must apply by itself.
5. ...
What is the expectation for this branch?
Thanks,
--
Nélio Laranjeiro
6WIND
next reply other threads:[~2017-02-15 10:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-15 10:23 Nélio Laranjeiro [this message]
2017-02-16 5:03 ` Yuanhan Liu
2017-02-16 8:21 ` Nélio Laranjeiro
2017-02-16 8:42 ` Yuanhan Liu
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=20170215102345.GU23344@autoinstall.dev.6wind.com \
--to=nelio.laranjeiro@6wind.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).