From: Junio C Hamano <gitster@pobox.com>
Date: Sun, 02 Dec 2007 18:53:33 GMT
Subject: Re: Corrupted (?) commit 6e6db85e confusing gitk
Message-ID: <7vir3hx70y.fsf@gitster.siamese.dyndns.org>
In-Reply-To: <5F1A20CC-7427-4E7A-AB95-E89C9FA17951@zib.de>

Steffen Prohaska <prohaska@zib.de> writes:

> I'd like to conclude with some questions:
>  - Is this commit corrupted?
>  - How was the commit created?
>  - Should "git fsck" detect such corruption?
>  - Should gitk more gracefully handle corrupted commits?

Yeah, I was wondering what that commit that records the change older
than git or myself come to life ;-)

I did rewrite the commit a few times, and it was some interaction
between the built-in commit series, git-rebase -i and git-am, but I do
not have the details, sorry.