From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Tommy Thorn <tommy-git@thorn.ws>
Cc: git@vger.kernel.org
Subject: Re: git bug: rebase fatal failure
Date: Fri, 16 May 2008 11:41:44 +0100 (BST) [thread overview]
Message-ID: <alpine.DEB.1.00.0805161139530.30431@racer> (raw)
In-Reply-To: <482BE5F7.2050108@thorn.ws>
Hi,
On Thu, 15 May 2008, Tommy Thorn wrote:
> I have large-ish repository (143 MB) where git rebase failed
> unexpectedly (see below). If anyone is interested in looking at this, I
> have left a copy of the repository at
> http://thorn.ws/git-fatal-rebase-error.tar.gz
I can reproduce. It seems that our diff machinery generates a file that
adds a file with 10668 lines, but says 10669 lines in the hunk header.
It is a .info file, so I suspect strange things going on with
non-printable ASCII characters.
I'm on it,
Dscho
next prev parent reply other threads:[~2008-05-16 10:42 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-15 7:27 git bug: rebase fatal failure Tommy Thorn
2008-05-16 10:41 ` Johannes Schindelin [this message]
2008-05-16 11:01 ` Johannes Schindelin
2008-05-16 13:03 ` [PATCH] mailsplit and mailinfo: gracefully handle NUL characters Johannes Schindelin
2008-05-16 14:03 ` Avery Pennarun
2008-05-16 14:05 ` David Kastrup
2008-05-16 14:32 ` Johannes Schindelin
2008-05-16 14:56 ` Avery Pennarun
2008-05-16 23:59 ` Johannes Schindelin
2008-05-17 0:06 ` Tommy Thorn
2008-05-17 0:26 ` Johannes Schindelin
2008-05-17 10:07 ` Stephen R. van den Berg
2008-05-17 10:18 ` Johannes Schindelin
[not found] ` <200805161539.29259.brian.foster@innova-card.com>
2008-05-16 14:07 ` Brian Foster
2008-05-16 14:14 ` David Kastrup
2008-05-16 14:29 ` Johannes Schindelin
2008-05-16 14:33 ` David Kastrup
2008-05-21 18:08 ` Junio C Hamano
2008-05-22 10:38 ` Johannes Schindelin
2008-05-22 17:44 ` Junio C Hamano
2008-05-23 11:21 ` Johannes Schindelin
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=alpine.DEB.1.00.0805161139530.30431@racer \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=tommy-git@thorn.ws \
/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