Hi Brian, On Wed, Apr 16, 2008 at 11:45:39AM +0200, Brian Foster wrote: > David Kastrup <dak@xxxxxxx> sensibly asks: > > Brian Foster <brian.foster@xxxxxxxxxxxxxxx> 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 -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
