Re: Corrupted (?) commit 6e6db85e confusing gitk

From: Michael Gebetsroither <gebi@sbox.tugraz.at>
Date: Dec 2, 2007, 22:59 UTC
Message-ID: <fivdfu$smr$1@ger.gmane.org>
In-Reply-To: <7vmyssvn55.fsf@gitster.siamese.dyndns.org>

* Junio C Hamano <gitster@pobox.com> wrote:

> Yeah, that change does look like a hack now we look at it again.  It
> would have been much cleaner to make the caller accept the default
> behaviour of fmt_ident() and strip out the part it does not want from
> the result.  That way, the damage would have been much contained.

Last hg2git from repo.or.cz does it (it uses git-fast-import).

Just tried to convert lastes mercurial repos to git and the resulting git repos can't be displayed with gitk.

git fsck --full gives many "bad commit date in xxxx"

% git cat-file commit f7900d59930d796c4739452cf68ca9c08a921b5d | sed % '/^$/,//d' tree 4fb3636148433dcd368fc2dfa20247cb281e2ff8 parent 6ea0491f4ebb13003d15c6fc478d92cbe1201902 author Mathieu Clabaut <mathieu.clabaut@gmail.com> <"Mathieu Clabaut <mathieu.clabaut@gmail.com>"> 1153937514 +0200 committer Mathieu Clabaut <mathieu.clabaut@gmail.com> <"Mathieu Clabaut <mathieu.clabaut@gmail.com>"> 1153937514 +0200

But the new hg2git is _amazingly_ fast, converts the whole mercurial repos got git in just 1min :).

cu, michael

-- 
It's already too late!