David Kastrup <dak@gnu.org> sensibly asks:
Show 19 quoted lines
> 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
>
> From the git-clone manpage
> --shared, -s [ ... ]
>
> Did you use something like that?
NO, not for any of the clones I've made. basically,
I've tried:
git clone git://SERVER/PATH # on a remote machine
git clone --bare git://SERVER/PATH # on a remote machine
git clone /FULL/PATH # on the SERVER
git clone --bare /FULL/PATH # on the SERVER
and possibly a few other variants along similar lines.
nothing fancy. just the sort of routine simple stuff
you'd expect to work, and expect(?) a newbie to use.
none of my clones, nor the repro on SERVER I'm trying
to clone, have any .../objects/info/alternates
cheers!
-blf-
--
"How many surrealists does it take to | Brian Foster
change a lightbulb? Three. One calms | somewhere in south of France
the warthog, and two fill the bathtub | Stop E$$o (ExxonMobil)!
with brightly-coloured machine tools." | http://www.stopesso.com
