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

From: Dmitry Potapov <dpotapov@gmail.com>
Date: Apr 16, 2008, 11:26 UTC
Message-ID: <20080416112646.GA4831@dpotapov.dyndns.org>
In-Reply-To: <a537dd660804160245q5fd3a0d9jc37802765601b176@mail.gmail.com>

Hi Brian,

On Wed, Apr 16, 2008 at 11:45:39AM +0200, Brian Foster wrote:

Show 15 quoted lines

> David Kastrup <dak@gnu.org> sensibly asks:
> >  Brian Foster <brian.foster@innova-card.com> writes:
> >  >  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:
> >  >
> >  >       $ git-fsck --full   # clone (same command for bare repo is Ok)
> >  >       broken link from  commit dd3f3c0636cfd50719c706b030db5473b0270add
> >  >                     to  commit 0fed9c2eb14eee47097e1d870fe8e55a6430edeb
> >  >       missing commit fb57c018d15005b60f104e57f198ff34a6035b99
> >  >       missing commit f8947cb0b5fe605e6cb5f73c89f262424b64ef3c
> >  >       missing commit 0fed9c2eb14eee47097e1d870fe8e55a6430edeb
> >  >       missing commit dff364d8da15be0b856a174062fb785acb1c363e

I suspect your original git repository has info/grafts

Dmitry