Hi, On Wed, 10 Oct 2007, Han-Wen Nienhuys wrote: > 2007/10/10, Lars Hjemli <hjemli@xxxxxxxxx>: > > On 10/10/07, J. Bruce Fields <bfields@xxxxxxxxxxxx> wrote: > > > On Wed, Oct 10, 2007 at 06:30:02PM -0300, Han-Wen Nienhuys wrote: > > > > could it be that GC does not handle cyclic alternates correctly? > > > > > > Does it handle alternates at all? If you run git-gc on a repository > > > which other repositories get objects from, then my impression was > > > that bad things happen. > > > > > > > AFAIK 'git gc' is safe, while 'git gc --prune' will remove loose > > (unreferenced) objects. > > Yes, I think that in this case, gc --prune was run accidentally, but > given that the history of the program invoking git just died, I'm not > sure how to figure that out. > > Maybe gc --prune could follow the alternates and abort if a cycle was > detected? I think we talked about this quite some time ago, and the resolution was that it is too hard. Now that it bit somebody in real life, I think we have to try harder. And probably the best place to check would be git-prune, not git-gc, since that is the program (called by gc) that most probably killed your repo. Come to think of it, it should probably be part of git-repack, too. Will try to cobble up a patch, Dscho - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
