On Fri, 2006-12-01 at 14:13, Linus Torvalds wrote: > So this is why it's really important that the submodule really is a git > repository in its own right, and why committing stuff in the supermodule > NEVER affect the submodule itself directly (it might _cause_ you to also > do a commit in the submodule indirectly, but the submodule commit MUST be > totally independent, and stand on its own). An implication of this is that the entire administrative responsibility for having some super-sub module interaction lies entirely with the supermodule. Why not have a "glue" object at the "stub"-interface of the supermodule tree that provides policy mappings to the sub-modules. Perhaps indicating git URL location, mappings of branch names between super- and sub- modules, special commit SHA1s, user policy or config choices at the boundary, and things like that. Is that the sort of direction we are headed? jdl - 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