Re: git blame crashes with internal error

From: Johannes Schindelin <johannes.schindelin@gmx.de>
Date: Oct 14, 2007, 17:32 UTC
Message-ID: <Pine.LNX.4.64.0710141830050.25221@racer.site>
In-Reply-To: <20071014152327.GA24003@atjola.homenet>

Hi,

On Sun, 14 Oct 2007, Bj?rn Steinbrink wrote:

Show 11 quoted lines

> On 2007.10.14 16:51:46 +0200, Andreas Ericsson wrote:
> > Bj?rn Steinbrink wrote:
> >> I tried all git releases from 1.5.3 to 1.5.3.4 as well as the current
> >> master and all of them crashed. A small shell script to reproduce the
> >> problem is attached.
> >
> > Manual bisect? Ugh. This *is* the century of the competent developer
> > tools, you know... ;-)
> 
> Then, how do I search for a good version with git bisect if I only have
> the one data-point "master is bad"?

AFAIK Junio introduced the option to start with just a bad commit, and no known "good" one.

Yep, just found it. Since v1.5.2-rc0~77^2(git-bisect: allow bisecting with only one bad commit.) it is supported.

>From the commit message:

    This allows you to say:

        git bisect start
        git bisect bad $bad
        git bisect next

I don't know if it is in the documentation (I rarely read it), so if it is missing, it would be nice if you could add the description there.

Ciao, Dscho