git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Björn Steinbrink" <B.Steinbrink@gmx.de>
To: Andreas Ericsson <ae@op5.se>
Cc: gitster@pobox.com, git@vger.kernel.org
Subject: Re: git blame crashes with internal error
Date: Sun, 14 Oct 2007 17:23:27 +0200	[thread overview]
Message-ID: <20071014152327.GA24003@atjola.homenet> (raw)
In-Reply-To: <47122D02.9060204@op5.se>

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"?

All I tried when testing those 5 versions was trying to find a good
version so that I can actually do an automatic bisect. And I stopped at
1.5.3 because I figured that my test-case is probably just pretty
uncommon and was basically always broken.

Another manual "bisect" shows that 1.5.0 also crashes and as 1.4.0
doesn't even want to read my git git repository, I don't intend to go
even further backwards in the history to find a good commit, unless
someone tells me that it is a really good idea or how to automate
finding a good commit in a sane way.

Björn

  parent reply	other threads:[~2007-10-14 15:23 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-14 14:36 git blame crashes with internal error Björn Steinbrink
2007-10-14 14:51 ` Andreas Ericsson
2007-10-14 14:56   ` David Kastrup
2007-10-14 16:50     ` Pierre Habouzit
2007-10-14 15:23   ` Björn Steinbrink [this message]
2007-10-14 17:32     ` Johannes Schindelin
2007-10-14 20:18       ` Björn Steinbrink
2007-10-14 20:21         ` Johannes Schindelin
2007-10-14 16:37 ` Alex Riesen
2007-10-14 17:33   ` Alex Riesen
2007-10-14 17:51   ` Johannes Schindelin
2007-10-15 15:39 ` Linus Torvalds

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20071014152327.GA24003@atjola.homenet \
    --to=b.steinbrink@gmx.de \
    --cc=ae@op5.se \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).