Stefan Beller <sbel...@google.com> writes: > It doesn't even have to be a submodule related thing at all. > > I can imagine that `git gc` could learn to walk nested repos > (not submodules, just repos on disk inside the work tree). > And for that use case we'd maybe want to have a setting > to pack the nested repos more aggressively than the toplevel repo. > > (Not sure if there would be a use case or such a thing, but it is the > first I came up with)
I do not think we are in the business of mucking with "dump of unrelated collections of repositories, whose inter-relationship the user did not tell us anything about". I however can foresee a value in "git gc --recurse-submodules", and I could see users may want to gc different submodules in different ways (which again brings us back to your "submodule group" thing). -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
