From: David Kastrup <dak@gnu.org>
To: git@vger.kernel.org
Subject: Re: fsck --full is Ok, but clones are not, "missing commits"?!
Date: Wed, 16 Apr 2008 11:14:43 +0200 [thread overview]
Message-ID: <86lk3ecgak.fsf@lola.quinscape.zz> (raw)
In-Reply-To: 20080416063739.4B72647879@blf.utvinternet.co.uk
Brian Foster <brian.foster@innova-card.com> writes:
> (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:
>
> $ 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
When the repository to clone is on the local machine,
instead of using hard links, automatically setup
.git/objects/info/alternates to share the objects with
the source repository. The resulting repository starts
out without any object of its own. NOTE: this is a
possibly dangerous operation; do not use it unless you
understand what it does. If you clone your repository
using this option, then delete branches in the source
repository and then run git-gc(1) using the --prune
option in the source repository, it may remove objects
which are referenced by the cloned repository.
Did you use something like that?
--
David Kastrup
next prev parent reply other threads:[~2008-04-16 9:15 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20080416062925.8028e952@zebulon.innova-card.com>
2008-04-16 6:37 ` fsck --full is Ok, but clones are not, "missing commits"?! Brian Foster
2008-04-16 9:14 ` David Kastrup [this message]
2008-05-05 4:25 ` Bryan Donlan
[not found] ` <200805051608.55200.brian.foster@innova-card.com>
2008-05-05 14:44 ` Brian Foster
2008-05-05 15:12 ` Johannes Sixt
[not found] ` <200805061231.30135.brian.foster@innova-card.com>
2008-05-06 10:58 ` Brian Foster
2008-05-06 11:12 ` Johannes Sixt
[not found] <200804161128.04245.brian.foster@innova-card.com>
2008-04-16 9:45 ` Brian Foster
2008-04-16 11:26 ` Dmitry Potapov
[not found] <200804161334.17748.brian.foster@innova-card.com>
2008-04-16 11:48 ` Brian Foster
2008-04-16 13:22 ` Johannes Sixt
2008-04-16 14:25 ` Dmitry Potapov
2008-04-16 14:56 ` Johannes Sixt
2008-04-16 16:17 ` Dmitry Potapov
2008-04-16 16:47 ` Jakub Narebski
2008-04-17 6:18 ` Johannes Sixt
[not found] <200804161626.44174.brian.foster@innova-card.com>
2008-04-16 15:04 ` Brian Foster
2008-04-16 15:22 ` Johannes Sixt
2008-04-16 16:11 ` Brandon Casey
[not found] ` <200804171643.15504.brian.foster@innova-card.com>
2008-04-17 14:53 ` Brian Foster
2008-04-17 15:41 ` Brandon Casey
[not found] ` <200804180943.20933.brian.foster@innova-card.com>
2008-04-18 8:41 ` Brian Foster
2008-04-18 8:55 ` Johannes Sixt
[not found] ` <200804181114.47067.brian.foster@innova-card.com>
2008-04-18 9:29 ` Brian Foster
2008-04-16 17:15 ` Dmitry Potapov
[not found] <200804171756.39911.brian.foster@innova-card.com>
2008-04-17 18:44 ` Brian Foster
[not found] <20080506115224.79802c7c@zebulon.innova-card.com>
2008-05-06 12:17 ` Johannes Sixt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86lk3ecgak.fsf@lola.quinscape.zz \
--to=dak@gnu.org \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).