From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: git trees organization Date: Thu, 14 Sep 2017 10:22:23 +0200 Message-ID: <5858182.HmkBWfGZLK@xps> References: <2737351.pD9poAUtZC@xps> <20170913145402.GA2481@6wind.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: Bruce Richardson , dev@dpdk.org, techboard@dpdk.org To: Stephen Hemminger , Adrien Mazarguil , Ferruh Yigit Return-path: In-Reply-To: List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 14/09/2017 04:25, Stephen Hemminger: > Bisecting a tree with lots of subtree merges is terrible. That is why Linus > rebases and doesn't directly take linux-next I agree, bisecting with subtree merges is not pleasant at all. That's why I chose the rebase method until now. Adrien mentioned some drawbacks with the rebase method. Ferruh mentioned some drawbacks and some advantages of rebase. Stephen mentioned another advantage of rebase. Such decisions are really difficult. One thing is sure: there will be always someone unhappy, no matter the decision :) When we want to take such decision or re-consider it, we ask the techboard to vote...