From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ozlabs.org (ozlabs.org [203.10.76.45]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "mx.ozlabs.org", Issuer "CA Cert Signing Authority" (verified OK)) by bilbo.ozlabs.org (Postfix) with ESMTPS id C442BB71C9 for ; Sun, 21 Jun 2009 17:26:08 +1000 (EST) Received: from terminus.zytor.com (terminus.zytor.com [198.137.202.10]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by ozlabs.org (Postfix) with ESMTPS id 0AE66DDDA0 for ; Sun, 21 Jun 2009 17:26:06 +1000 (EST) Message-ID: <4A3DDB27.2000500@zytor.com> Date: Sun, 21 Jun 2009 00:03:03 -0700 From: "H. Peter Anvin" MIME-Version: 1.0 To: Frans Pop Subject: Re: Badness on the Warp References: <20090620154824.72b5cd50@lappy.seanm.ca> <200906202256.46073.elendil@planet.nl> In-Reply-To: <200906202256.46073.elendil@planet.nl> Content-Type: text/plain; charset=UTF-8 Cc: linuxppc-dev@ozlabs.org, linux-kernel@vger.kernel.org, Sean MacLennan List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Frans Pop wrote: > > The fact that your bisect ended at a merge essentially means that it is > invalid. As a merge does not introduce any actual change (unless it > includes changes to resolve conflicts), it normally cannot be the cause > of a regression. > Sort of. You can have a "bum merge" where code conflicts logically, even if it isn't visible as a conflict in git. Furthermore, of course, you can have misresolved actual conflicts. -hpa -- H. Peter Anvin, Intel Open Source Technology Center I work for Intel. I don't speak on their behalf. From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754511AbZFUHDW (ORCPT ); Sun, 21 Jun 2009 03:03:22 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753627AbZFUHDN (ORCPT ); Sun, 21 Jun 2009 03:03:13 -0400 Received: from terminus.zytor.com ([198.137.202.10]:55210 "EHLO terminus.zytor.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753020AbZFUHDM (ORCPT ); Sun, 21 Jun 2009 03:03:12 -0400 Message-ID: <4A3DDB27.2000500@zytor.com> Date: Sun, 21 Jun 2009 00:03:03 -0700 From: "H. Peter Anvin" User-Agent: Thunderbird 2.0.0.14 (X11/20080501) MIME-Version: 1.0 To: Frans Pop CC: Sean MacLennan , linuxppc-dev@ozlabs.org, linux-kernel@vger.kernel.org Subject: Re: Badness on the Warp References: <20090620154824.72b5cd50@lappy.seanm.ca> <200906202256.46073.elendil@planet.nl> In-Reply-To: <200906202256.46073.elendil@planet.nl> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Frans Pop wrote: > > The fact that your bisect ended at a merge essentially means that it is > invalid. As a merge does not introduce any actual change (unless it > includes changes to resolve conflicts), it normally cannot be the cause > of a regression. > Sort of. You can have a "bum merge" where code conflicts logically, even if it isn't visible as a conflict in git. Furthermore, of course, you can have misresolved actual conflicts. -hpa -- H. Peter Anvin, Intel Open Source Technology Center I work for Intel. I don't speak on their behalf.