From: Dmitry Potapov <dpotapov@gmail.com>
To: Brian Foster <blf@utvinternet.ie>
Cc: git@vger.kernel.org
Subject: Re: Re: fsck --full is Ok, but clones are not, "missing commits"?!
Date: Wed, 16 Apr 2008 15:26:46 +0400 [thread overview]
Message-ID: <20080416112646.GA4831@dpotapov.dyndns.org> (raw)
In-Reply-To: <a537dd660804160245q5fd3a0d9jc37802765601b176@mail.gmail.com>
Hi Brian,
On Wed, Apr 16, 2008 at 11:45:39AM +0200, Brian Foster wrote:
> 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
next prev parent reply other threads:[~2008-04-16 11:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200804161128.04245.brian.foster@innova-card.com>
2008-04-16 9:45 ` Re: fsck --full is Ok, but clones are not, "missing commits"?! Brian Foster
2008-04-16 11:26 ` Dmitry Potapov [this message]
[not found] <20080416062925.8028e952@zebulon.innova-card.com>
2008-04-16 6:37 ` Brian Foster
2008-04-16 9:14 ` David Kastrup
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080416112646.GA4831@dpotapov.dyndns.org \
--to=dpotapov@gmail.com \
--cc=blf@utvinternet.ie \
--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.
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 NNTP newsgroup(s).