FWIW, here's my view on this issue. On Sun, Nov 26, 2006 at 12:49:08AM +0100, Yann Dirson wrote: > 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. A commit should record the content changes that have been made, not change any content itself. Some VCSs change the contents of a file when you commit them (e.g., keyword substitution). Git, rightly, doesn't do that. Likewise, when you commit in the superproject, it should simply record the changes to the "content" of the subproject and not change it. And the content of the subproject is a commit, so a commit in the superproject should not change the content of the subproject by creating another commit in the subproject. skimo - 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