From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: Proposal for a new Committer model Date: Thu, 24 Nov 2016 10:17:09 +0100 Message-ID: <1598958.4NzbtDc3LW@xps13> References: <20161123201330.GD6961@hmsreliant.think-freely.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: Ferruh Yigit , dev@dpdk.org, "Mcnamara, John" To: Neil Horman Return-path: Received: from mail-wm0-f54.google.com (mail-wm0-f54.google.com [74.125.82.54]) by dpdk.org (Postfix) with ESMTP id 079C04A59 for ; Thu, 24 Nov 2016 10:17:10 +0100 (CET) Received: by mail-wm0-f54.google.com with SMTP id g23so106479819wme.1 for ; Thu, 24 Nov 2016 01:17:10 -0800 (PST) In-Reply-To: <20161123201330.GD6961@hmsreliant.think-freely.org> List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 2016-11-23 15:13, Neil Horman: > Can either you or thomas provide some detail as to how you are doing patch > management between trees (details of the commands you use are what I would be > interested in). It sounds to me like there may be some optimization to be made > here before we even make changes to the subtrees. Until now, we preferred avoiding merge commits. That's why I rebase sub-trees to integrate them in the mainline. As Ferruh explained, it does not require more work because sub-trees are regularly rebased anyway. And I use a script to keep original committer name and date. Hope it's clear now