{"thread":{"id":"13135","subject":"Re: Re: fsck --full is Ok, but clones are not, \"missing commits\"?!","startedAt":"2008-04-16T09:45:39Z","lastAt":"2008-04-16T11:26:46Z","messageCount":2,"participants":["Brian Foster","Dmitry Potapov"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"74536","messageId":"a537dd660804160245q5fd3a0d9jc37802765601b176@mail.gmail.com","threadId":"13135","inReplyTo":"200804161128.04245.brian.foster@innova-card.com","subject":"Re: Re: fsck --full is Ok, but clones are not, \"missing commits\"?!","fromName":"Brian Foster","fromEmail":"blf@utvinternet.ie","sentAt":"2008-04-16T09:45:39Z","receivedAt":"2008-04-16T09:45:39Z","isPatch":false,"sender":{"key":"blf@utvinternet.ie","avatar":null},"body":"David Kastrup <dak@gnu.org> sensibly asks:\n>  Brian Foster <brian.foster@innova-card.com> writes:\n>  >  I've recently inherited a bare git repository,\n>  >  which, as far as I can tell (I'm something of\n>  >  a newbie with git), seems Ok: `git fsck --full'\n>  >  does not report any problems.    however, any\n>  >  clones I make from it are not Ok:\n>  >\n>  >       $ git-fsck --full   # clone (same command for bare repo is Ok)\n>  >       broken link from  commit dd3f3c0636cfd50719c706b030db5473b0270add\n>  >                     to  commit 0fed9c2eb14eee47097e1d870fe8e55a6430edeb\n>  >       missing commit fb57c018d15005b60f104e57f198ff34a6035b99\n>  >       missing commit f8947cb0b5fe605e6cb5f73c89f262424b64ef3c\n>  >       missing commit 0fed9c2eb14eee47097e1d870fe8e55a6430edeb\n>  >       missing commit dff364d8da15be0b856a174062fb785acb1c363e\n>\n>  From the git-clone manpage\n>         --shared, -s  [ ... ]\n>\n>  Did you use something like that?\n\n NO, not for any of the clones I've made.  basically,\n I've tried:\n\n   git clone        git://SERVER/PATH   # on a remote machine\n   git clone --bare git://SERVER/PATH   # on a remote machine\n   git clone        /FULL/PATH          # on the SERVER\n   git clone --bare /FULL/PATH          # on the SERVER\n\n and possibly a few other variants along similar lines.\n nothing fancy.  just the sort of routine simple stuff\n you'd expect to work, and expect(?) a newbie to use.\n\n none of my clones, nor the repro on SERVER I'm trying\n to clone, have any .../objects/info/alternates\n\ncheers!\n\t-blf-\n-- \n\"How many surrealists does it take to    |  Brian Foster\n change a lightbulb?  Three.  One calms  |  somewhere in south of France\n the warthog, and two fill the bathtub   |     Stop E$$o (ExxonMobil)!\n with brightly-coloured machine tools.\"  |       http://www.stopesso.com\n"},{"id":"74539","messageId":"20080416112646.GA4831@dpotapov.dyndns.org","threadId":"13135","inReplyTo":"a537dd660804160245q5fd3a0d9jc37802765601b176@mail.gmail.com","subject":"Re: Re: fsck --full is Ok, but clones are not, \"missing commits\"?!","fromName":"Dmitry Potapov","fromEmail":"dpotapov@gmail.com","sentAt":"2008-04-16T11:26:46Z","receivedAt":"2008-04-16T11:26:46Z","isPatch":false,"sender":{"key":"dpotapov@gmail.com","avatar":"https://avatars.githubusercontent.com/u/6568595?v=4"},"body":"Hi Brian,\n\nOn Wed, Apr 16, 2008 at 11:45:39AM +0200, Brian Foster wrote:\n> David Kastrup <dak@gnu.org> sensibly asks:\n> >  Brian Foster <brian.foster@innova-card.com> writes:\n> >  >  I've recently inherited a bare git repository,\n> >  >  which, as far as I can tell (I'm something of\n> >  >  a newbie with git), seems Ok: `git fsck --full'\n> >  >  does not report any problems.    however, any\n> >  >  clones I make from it are not Ok:\n> >  >\n> >  >       $ git-fsck --full   # clone (same command for bare repo is Ok)\n> >  >       broken link from  commit dd3f3c0636cfd50719c706b030db5473b0270add\n> >  >                     to  commit 0fed9c2eb14eee47097e1d870fe8e55a6430edeb\n> >  >       missing commit fb57c018d15005b60f104e57f198ff34a6035b99\n> >  >       missing commit f8947cb0b5fe605e6cb5f73c89f262424b64ef3c\n> >  >       missing commit 0fed9c2eb14eee47097e1d870fe8e55a6430edeb\n> >  >       missing commit dff364d8da15be0b856a174062fb785acb1c363e\n\nI suspect your original git repository has info/grafts\n\nDmitry\n"}]}