From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by dpdk.org (Postfix) with ESMTP id D3636160 for ; Sun, 3 Jun 2018 19:52:39 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 546DE21AE2; Sun, 3 Jun 2018 13:52:38 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Sun, 03 Jun 2018 13:52:38 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=mesmtp; bh=/GxNCEypJSs4kdYMSUqtX2Av2k ygI9QnVdVNx10Zbf4=; b=sb25vcgk/o/HJEo2DP6BE/9+Dqq4snG8qhP+31MkSi gph4xbaCq1Iy/Du3IEAnHOBr1zbWSwej1hiyJ6wMf1xcKt8CUTfxQHWF5bw7ll9Q EjpmVHh9ClfknTQr0yaxzRXFEWm7KmCYNyoxUKVMQ6tBPLheKng/BBWEe9JEizqs M= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=/GxNCE ypJSs4kdYMSUqtX2Av2kygI9QnVdVNx10Zbf4=; b=PNl5WIRxkPs3Z9f3jJy27u 1Hg8KRwaPu+pcSGgDP2SRvwV/Lq68WGAEoHsQd9hjA6aBcEXncU40cu4qSd5CJEI bMFprG2XDM+ERHeQWJ82sEL16xaSgFNeUDZBzgQdtG9hXU5DxW8jf0Y8UdPRvq/Z 6hNislIsQWWqTKZSClK4MpP0Tpjtm6i9GWpWxtG/ylLsCx+Osu3lbujR+jmsJvyW TVlQndI5lyTobNBbx7X4dwAff36leXE6usgWMR5sk7PDy1jYjpkbJACxSWAmR7Dg GhOZdw/NEq3vvNbaR2ckIV+GWFCTIIyvlzUCx++ZASeG+YYNfpPjN73qwp6wjNZg == X-ME-Proxy: X-ME-Proxy: X-ME-Proxy: X-ME-Proxy: X-ME-Proxy: X-ME-Proxy: X-ME-Sender: Received: from xps.localnet (206.203.136.77.rev.sfr.net [77.136.203.206]) by mail.messagingengine.com (Postfix) with ESMTPA id 6677C10266; Sun, 3 Jun 2018 13:52:36 -0400 (EDT) From: Thomas Monjalon To: Yuanhan Liu Cc: Kevin Traynor , bluca@debian.org, Yongseok Koh , stable@dpdk.org Date: Sun, 03 Jun 2018 19:52:32 +0200 Message-ID: <10687100.Bg4LDGQuS2@xps> In-Reply-To: <20180602051334.5vpjgalrfhlfjvk3@yuanhanliu-NB0.tencent.com> References: <20180527053517.lv24ma5n452na3cm@yuanhanliu-NB0.tencent.com> <3962613.dM9x5Q0JGJ@xps> <20180602051334.5vpjgalrfhlfjvk3@yuanhanliu-NB0.tencent.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-stable] 17.11.3 (LTS) patches review and test X-BeenThere: stable@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches for DPDK stable branches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Jun 2018 17:52:40 -0000 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.