Andy Parkins wrote: >> You still don't have a totally separated repository then, because >> you can't do a reachability analysis in the submodule repository alone. > > I'm going to guess by reachability analysis, you mean that the submodule > doesn't know that some of it's commits are referenced by the supermodule. As > I suggested elsewhere in the thread, that's easily fixed by making a > refs/supermodule/commitXXXX file for each supermodule commit that references > as particular submodule commit. Then you can git-prune, git-fsck whenever > you want. I think it would be better resolve this in universal way by adding to git repository layout the optional "borrowers" file, which would protect against pruning objects that are referenced by repositories which have given repository as one of the "alternates". By the way, how to slurp all the objects from alternates into repo object repository? -- Jakub Narebski Warsaw, Poland ShadeHawk on #git - 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