From mboxrd@z Thu Jan 1 00:00:00 1970 From: "H. Peter Anvin" Subject: Re: [RFC/PATCH 1/1] format-patch: add an option to record base tree info Date: Tue, 23 Feb 2016 01:23:19 -0800 Message-ID: <56CC2507.7060300@zytor.com> References: <1456109938-8568-1-git-send-email-xiaolong.ye@intel.com> <1456109938-8568-2-git-send-email-xiaolong.ye@intel.com> <20160223014741.GA21025@wfg-t540p.sh.intel.com> <20160223091740.GA3830@wfg-t540p.sh.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Cc: Xiaolong Ye , git@vger.kernel.org, ying.huang@intel.com, philip.li@intel.com, julie.du@intel.com, Linus Torvalds , "Eric W. Biederman" , Christoph Hellwig , Dan Carpenter , LKML To: Fengguang Wu , Junio C Hamano X-From: linux-kernel-owner@vger.kernel.org Tue Feb 23 10:24:00 2016 Return-path: Envelope-to: glk-linux-kernel-3@plane.gmane.org Received: from vger.kernel.org ([209.132.180.67]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1aY9CJ-0006dF-KO for glk-linux-kernel-3@plane.gmane.org; Tue, 23 Feb 2016 10:23:59 +0100 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751760AbcBWJXt (ORCPT ); Tue, 23 Feb 2016 04:23:49 -0500 Received: from terminus.zytor.com ([198.137.202.10]:58824 "EHLO mail.zytor.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750919AbcBWJXo (ORCPT ); Tue, 23 Feb 2016 04:23:44 -0500 Received: from tazenda.hos.anvin.org ([IPv6:2601:646:8f02:f890:e269:95ff:fe35:9f3c]) (authenticated bits=0) by mail.zytor.com (8.15.2/8.14.5) with ESMTPSA id u1N9NO3X006734 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Tue, 23 Feb 2016 01:23:25 -0800 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0 In-Reply-To: <20160223091740.GA3830@wfg-t540p.sh.intel.com> Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Archived-At: On 02/23/16 01:17, Fengguang Wu wrote: > > However we are facing a new situation: in test robot POV, IMHO there > are values to test exactly the same tree as the patch submitter. > Otherwise the robot risks > > - false negative: failing to apply and test some patches > - false positive: sending wrong bug reports due to guessed wrong base tree > Wouldn't the important part here be the git hash, rather than the tree? If you have the same hash then it by definition is the same contents? -hpa