On Sat, Nov 25, 2006 at 11:30:47AM -0800, Linus Torvalds wrote: > The git trees are _independent_. That's important. I'm not sure how independant you mean them to be. The approach I've tried to describe so far assumes that, although you can look at each submodule independently from the supermodule or any other submodule, you can still look at the supermodule as a single tree of it own. Eg, so that if one part of an appliance/ modules ends up promoted to a lib/ module, GIT can still show that as a move within the supermodule. If we insist that the submodules get committed independently before we make a supermodule commit tying those together, I fear it may make things like such "move/copy detection" more tricky ? Also, I'd rather expect "git-commit -a" outside of any submodule to commit everything in the supermodule, triggering submodule commits as an intermediate step when needed - just like "git-commit -a" does not require to manually specify subdirectories to inclue in the commit. I'd rather expect a special flag to exclude submodules from a commit. Best regards, -- Yann. - 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