Re: Deprecation/Removal schedule

From: Alex Riesen <raa.lkml@gmail.com>
Date: Feb 6, 2007, 13:09 UTC
Message-ID: <81b0412b0702060509l1283fcb2j105a0580a718b2e0@mail.gmail.com>
In-Reply-To: <Pine.LNX.4.63.0702061202260.22628@wbgn013.biozentrum.uni-wuerzburg.de>

On 2/6/07, Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:

Show 17 quoted lines

> > > > git gc (repack -d of it) is too dangerous in a shared repo: it breaks
> > > > the repos which depend on the master repository, have sent (by some
> > > > means) some objects over to the master, and accidentally removed
> > > > the reference, and were pruned afterwards.
> > >
> > > We no longer call git-prune automatically in git-gc. You have to say
> > > "git-gc --prune" to trigger that behaviour.
> >
> > repack -d can lose objects, too:
> >
> > # fully packed test repo with 2 commits
>
> This is the culprit.
>
> The solution is very easy: do not --reference a repository which resets or
> deletes branches. IMHO this is all too obvious.
>

Or just do no repack in the referenced repo.

Anyway, the discussion outlived its usefulness. I have what I wanted (git fsck --unreachable), and nobody can force me to repack my shared repo, so the issue does not exist for the original poster.