patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Yuanhan Liu <yliu@fridaylinux.org>
Cc: Kevin Traynor <ktraynor@redhat.com>,
	bluca@debian.org, Yongseok Koh <yskoh@mellanox.com>,
	stable@dpdk.org
Subject: Re: [dpdk-stable] 17.11.3 (LTS) patches review and test
Date: Sun, 03 Jun 2018 19:52:32 +0200	[thread overview]
Message-ID: <10687100.Bg4LDGQuS2@xps> (raw)
In-Reply-To: <20180602051334.5vpjgalrfhlfjvk3@yuanhanliu-NB0.tencent.com>

02/06/2018 07:13, Yuanhan Liu:
> On Mon, May 28, 2018 at 12:30:01PM +0200, Thomas Monjalon wrote:
> > About the process, I wonder what should be the reference branch when backporting.
> > For example, could we use 18.02 stable branch to backport in 17.11?
> 
> We normally do (and should) not do that. For fixes not from the master
> branch, the author should send a patch alone to the stable list, telling
> the maintainer this patch is stable only and should apply to stable
> release X, Y, etc.

Why we should not base branch n-2 on branch n-1?
If a backport effort is done to port a patch from n to n-1,
we could re-use that for n-2, instead of re-doing the same effort.

  reply	other threads:[~2018-06-03 17:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-27  5:35 Yuanhan Liu
2018-05-28 10:16 ` Kevin Traynor
2018-05-28 10:30   ` Thomas Monjalon
2018-06-02  5:13     ` Yuanhan Liu
2018-06-03 17:52       ` Thomas Monjalon [this message]
2018-06-03 20:23         ` Luca Boccassi
2018-06-07 23:09 ` [dpdk-stable] [dpdk-dev] " Raslan Darawsheh
2018-06-08 14:29   ` Yuanhan Liu
2018-06-08 15:00 ` Bruce Richardson
2018-06-08 15:20   ` 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=10687100.Bg4LDGQuS2@xps \
    --to=thomas@monjalon.net \
    --cc=bluca@debian.org \
    --cc=ktraynor@redhat.com \
    --cc=stable@dpdk.org \
    --cc=yliu@fridaylinux.org \
    --cc=yskoh@mellanox.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).