From: Andreas Ericsson <ae@op5.se>
To: "Björn Steinbrink" <B.Steinbrink@gmx.de>
Cc: gitster@pobox.com, git@vger.kernel.org
Subject: Re: git blame crashes with internal error
Date: Sun, 14 Oct 2007 16:51:46 +0200 [thread overview]
Message-ID: <47122D02.9060204@op5.se> (raw)
In-Reply-To: <20071014143628.GA22568@atjola.homenet>
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... ;-)
--
Andreas Ericsson andreas.ericsson@op5.se
OP5 AB www.op5.se
Tel: +46 8-230225 Fax: +46 8-230231
next prev parent reply other threads:[~2007-10-14 14:52 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 [this message]
2007-10-14 14:56 ` David Kastrup
2007-10-14 16:50 ` Pierre Habouzit
2007-10-14 15:23 ` Björn Steinbrink
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=47122D02.9060204@op5.se \
--to=ae@op5.se \
--cc=B.Steinbrink@gmx.de \
--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).