Re: fsck --full is Ok, but clones are not, "missing commits"?!

From: Bryan Donlan <bdonlan@fushizen.net>
Date: May 5, 2008, 04:25 UTC
Message-ID: <20080505042546.GA7164@shion.is.fushizen.net>
In-Reply-To: <20080416063739.4B72647879@blf.utvinternet.co.uk>

On Wed, Apr 16, 2008 at 08:37:39AM +0200, Brian Foster wrote:

Show 8 quoted lines

>    (many many apologies if this turns into a double post,
>   there seems to have been problems with the 1st attempt?)
> 
>  I've recently inherited a bare git repository,
>  which, as far as I can tell (I'm something of
>  a newbie with git), seems Ok: `git fsck --full'
>  does not report any problems.    however, any
>  clones I make from it are not Ok:

 
[snip]

Show 9 quoted lines

>  explanations, suggestions, questions, &tc are all
>  very welcome.  (please keep in mind my current level
>  of knowledge/experience about git is very weak. ;-\ )
> 
>  this is all(?) using git 1.5.x (where the .x varies
>  depending on the machine in question); the distros
>  being used include ubuntu 7.10, FC-5, and probably
>  others.  (I'll check the filesystem tomorrow, but
>  I believe it's sane.)

Is there an info/grafts file? If the repository doesn't have sensitive information in it, it would probably be helpful to tarball it up and upload it somewhere, so we can take a look at things directly.