Thread (10 messages) flat view 10 messages, 5 authors, 2016-06-15

Re: git blame crashes with internal error

From: Johannes Schindelin <hidden>
Date: 2016-06-15 22:43:41

Hi,

On Sun, 14 Oct 2007, Bj?rn Steinbrink wrote:
On 2007.10.14 16:51:46 +0200, Andreas Ericsson wrote:
quoted
Bj?rn Steinbrink wrote:
quoted
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
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help