From: Jakub Narebski <jnareb@gmail.com>
Date: Wed, 16 Apr 2008 16:47:58 GMT
Subject: Re: fsck --full is Ok, but clones are not, "missing commits"?!
Message-ID: <fu5ajm$eaq$1@ger.gmane.org>
In-Reply-To: <20080416161742.GC3133@dpotapov.dyndns.org>

Dmitry Potapov wrote:

> On Wed, Apr 16, 2008 at 04:56:08PM +0200, Johannes Sixt wrote:
>> 
>> No. The reason why git clone'd repositories have problems is that
>> git-upload-pack sends a pack that does not contain the hidden objects;
but
>> since the cloned repository doesn't have the info/grafts, it tries to
look
>> up the hidden, now missing, objects, and fails.
> 
> In my experiment, there was no problem with hidden commits and objects
> as long as they presented in the original repository. Maybe, it is
> because I cloned it as locally using:
> 
>    git clone PATH-TO-ORIG-REPO PATH-TO-DEST-REPO
> 
> Maybe things would be as you say if I used git://

file:// should be enough.

-- 
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git