Re: fsck --full is Ok, but clones are not, "missing commits"?!
> 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;
>> since the cloned repository doesn't have the info/grafts, it tries to
Show 9 quoted lines
>> 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
Jakub Narebski <jnareb@gmail.com>