Re: git-svn bug?

From: Troy Telford <ttelford.groups@gmail.com>
Date: Nov 15, 2006, 22:55 UTC
Message-ID: <op.ti2xykijzidtg1@rygel.lnxi.com>
In-Reply-To: <7vejs4jshp.fsf@assigned-by-dhcp.cox.net>

On Wed, 15 Nov 2006 14:43:30 -0700, Junio C Hamano <junkio@cox.net> wrote:

Show 12 quoted lines

> "Troy Telford" <ttelford.groups@gmail.com> writes:
>
>> (using git 1.4.4, svn 1.3.1 on a SLES 10 box)
>> fatal: Not a valid object name  
>> 92e2e0c50bbbacb0a3426b2c0f8b3e043eb4830a~1
>> 32768 at /usr/lib/perl5/5.8.8/Memoize.pm line 269
>> ...
>> I couldn't find an object named
>> "92e2e0c50bbbacb0a3426b2c0f8b3e043eb4830a~1" in .git/
>
> Troy, do you have object 92e2e0c5?  Is it a root commit (i.e. a
> commit that does not have a parent)?

I'll have to admit I'm stabbing in the dark on how to get the correct answer this, but here goes:

* `git cat-file -t 92e2e0...` returns 'commit'
* 'git cat-file -p 92e2e0...` returns: (minus the header/footer asterisks)
*********************************************
tree 4b825dc642cb6eb9a060e54bf8d69288fbee4904
author unknown <unknown> 961088898 +0000
committer unknown <unknown> 961088898 +0000

New repository initialized by cvs2svn. *********************************************