Re: bisect gives strange answer

From: Junio C Hamano <junkio@cox.net>
Date: Aug 4, 2005, 18:43 UTC
Message-ID: <7v8xzh1r1v.fsf@assigned-by-dhcp.cox.net>
In-Reply-To: <20050804182717.GA2241@redhat.com>

Dave Jones <davej@redhat.com> writes:

> Errrrm, if you don't compile/test those intermediate versions,
> how do you know whether to tag it good/bad ?

I think Sanjoy is saying that they _were_ tested, and suspects that bisect didn't leave the right versions of the files in the work tree, so what was compiled and tested were not what bisect wanted to get tested. This is theory #2 in Sanjoy's post:

>> 2. git-bisect-script doesn't use -f when it does 'git checkout', so
>>    files that should be updated are not.  Right now I'm in the middle
>>    of recollecting the data with git-bisect-script using -f in all
>>    uses of git checkout (unless that is a really silly idea).

I find this explanation quite plausible, in case it is all my fault and I apologize for wasting kernel developers' time.