From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [PATCH] maintainers: add git repo information for libraries Date: Wed, 13 Mar 2019 08:35:37 +0100 Message-ID: <1776490.q62YuOiO2q@xps> References: <20190313015942.38143-1-ferruh.yigit@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: dev@dpdk.org To: Ferruh Yigit Return-path: Received: from wout2-smtp.messagingengine.com (wout2-smtp.messagingengine.com [64.147.123.25]) by dpdk.org (Postfix) with ESMTP id 116E137B0 for ; Wed, 13 Mar 2019 08:35:43 +0100 (CET) In-Reply-To: <20190313015942.38143-1-ferruh.yigit@intel.com> List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 13/03/2019 02:59, Ferruh Yigit: > Add target git sub-tree information for libraries, this is mainly to > reduce apply failures of the patches by automating target sub-tree > selection for a patch for automation. > > Also can be useful for developers to define which tree to base their > patches for specific library. > > Plan for DPDK Community lab is always try the main repo first, if patch > fails to apply, detect and try on that detected sub-tree. This is to > cover the case where sub-tree and main repo diverged and patch is based > on sub-tree. > Both because of above usage and to not create noise in file, git tree > information is not added for libraries which target main repo, which is > taken as default git repo. I think adding tree info for PMDs is redundant. Can we improve the script to smartly retrieve PMD tree, based on the T: line at the beginning of the PMD section?