Subject: Re: [bisected][mismerge?] Re: [microcode] 2.6.23.git pulled this
	morning oopses loading P4 microcode
From: Mike Galbraith <efault@gmx.de>
To: Samuel Thibault <samuel.thibault@ens-lyon.org>
Cc: LKML <linux-kernel@vger.kernel.org>
In-Reply-To: <1192762138.6838.13.camel@Homer.simpson.net>
References: <1192681533.7147.5.camel@Homer.simpson.net>
	 <1192730198.7182.18.camel@Homer.simpson.net>
	 <20071018223333.GD4153@implementation>
	 <1192762138.6838.13.camel@Homer.simpson.net>
Content-Type: text/plain; charset=ISO-8859-1
Date: Fri, 19 Oct 2007 12:18:19 +0200
Message-Id: <1192789099.7389.31.camel@Homer.simpson.net>
Mime-Version: 1.0
Content-Transfer-Encoding: 8bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1270
Lines: 32

On Fri, 2007-10-19 at 04:49 +0200, Mike Galbraith wrote: 
> On Thu, 2007-10-18 at 23:33 +0100, Samuel Thibault wrote:
> > Hi,
> > 
> > Mike Galbraith, le Thu 18 Oct 2007 19:56:38 +0200, a ?crit :
> > > The winner of a very long git bisect session:
> > > 
> > >     unicode diacritics support
> > 
> > Uh, I fail to see how that could have an impact, I've again checked the
> > boundaries, it looks fine, please people have a look.
> 
> I too was reluctant to believe the bisect result.  But...

Weeeell now, that skepticism is indeed well founded.  It's dontdiff.  A
diff of trees where defkeymap.c_shipped has been modified produces no
output.  Once a working tree has been afflicted by using diff+dontdiff
to update it, even overwriting the entire tree via git-archive doesn't
lead to a good build unless you also touch defkeymap.c_shipped
afterward.  In my case, the working tree remained buildable yet
thoroughly busted through a lengthy bisect and beyond.  That bisect
positively identified... the victim.

poo.

	-Mike

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/