On 2/6/07, Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote: > > > > 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. - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.htmlReceived on Wed Feb 07 00:10:08 2007
This archive was generated by hypermail 2.1.8 : 2007-02-07 00:11:59 EST