Re: git bisect enhancements?

From: Junio C Hamano <junkio@cox.net>
Date: Nov 30, 2005, 22:43 UTC
Message-ID: <7v3bldoiyq.fsf@assigned-by-dhcp.cox.net>
In-Reply-To: <1133386585.30767.34.camel@cashmere.sps.mot.com>

Jon Loeliger <jdl@freescale.com> writes:

Show 7 quoted lines

>...
> Two or three "good builds" into things, it proposes a
> new build at a272e24cc8751d125f9582befed0213a2a2b270f.
> Which I build and don't quite boot.  It hangs after
> the IDE probe, and before the i2c probe.  Bummer.
>
> These are not bugs I was looking for.  Move along.

This is not about your "bump", but one thing that may worthwhile to try is bisect enhancements Linus did a couple of days ago, to let you limit the number of commits tried by specifying the area you are interested in.

If may not help if only thing you know is that i2c probe is not what you are looking for, but if you know what area is suspect, say arch/powerpc and include/asm-powerpc (just taken randomly, I do not even know if you work in that area), it lets you say:

	$ git bisect reset
	$ git bisect start arch/powerpc include/asm-powerpc
        $ git bisect good v2.6.13-rc3
        $ git bisect bad master

What is interesting is that this cuts down the commits to be inspected to only the ones that touch the specified paths. So without the path specifier, you may need to bisect 5000 commits in total, but with the commits limited to the ones that touch these two example directories, you would need to bisect 247 commits, which is only a fraction of the original.