From: Antriksh Pany <antriksh.pany@gmail.com>
Date: Mon, 05 Jul 2010 08:37:20 GMT
Subject: Re: Patching bad commits
Message-ID: <AANLkTilrvCyCCIlU9M1HPAdxLREvyVL0pKyNsJR2wpN7@mail.gmail.com>
In-Reply-To: <AANLkTimAAtO9p2rQW4pITKQehhYF6pppBUgPxoyrLOvA@mail.gmail.com>

On Tue, Jun 29, 2010 at 3:53 AM, Avery Pennarun <apenwarr@gmail.com> wrote:
> On Mon, Jun 28, 2010 at 6:03 PM, Michael Witten <mfwitten@gmail.com> wrote:
>> Sometimes bisecting is less than useful because a number of commits
>> fail to build.
>>

You could automate the process of skipping certain commits when build fails.
  make || git bisect skip
Automatically mark commits as bad when your test fails:
  ./test || git bisect bad
Otherwise 'git bisect good' is what you do.

I think you can put these together in a loop that works automatically
without much user intervention.

Hope this helps.

Cheers
Antriksh Pany