Re: fsck --full is Ok, but clones are not, "missing commits"?!

From: Johannes Sixt <j.sixt@viscovery.net>
Date: Apr 16, 2008, 13:22 UTC
Message-ID: <4805FD7C.5000206@viscovery.net>
In-Reply-To: <a537dd660804160448w5ba28f13m8c081ebc2a71db91@mail.gmail.com>

Brian Foster schrieb:

Show 6 quoted lines

> Dmitry Potapov <dpotapov@gmail.com> correctly deduced:
>>  I suspect your original git repository has info/grafts
> 
> hi Dmitry,
> 
>  bingo!  YES, it does:

...

>  the goal is to put things into a sane state so any new
>  clones are healthy.  there's only one(?) existing clone,
>  which may or may not be(? become?) an issue.

Just move info/grafts out of the way and you *may* be all set. Don't delete it - there might be a reason that the file exists.

However!

You might observe one or more of the following:

- Parts of the history are missing. The reason is that the grafts were
used to "splice" histories that are actually independent.

- Previously unkown (to you) parts of the history are now visible. Then
the grafts were used to hide these parts.

- The repository is broken. Then 'git repack -f -d -a' was done while the
grafts were in effect (and obviously the grafts had hidden parts of the
history, which are now no longer available).

Your best bet is to run 'git filter-branch --tag-name-filter cat -- --all' on *a copy* of your bare repository (with info/grafts in place). (Read the warning about --tag-name-filter in the man page first.)

-- Hannes