One of the open source projects I work on (CC'd) recently moved to git, but we're having some slight problems, and I believe that it's the fault of git's UI in this case. We're using git submodules for the contributing libraries. When I commit changes to those contribs, it correctly shows in the parent repository that those folders have different revisions than what's currently committed. However, if someone pulls those changes, it doesn't automatically update the contribs to match the committed version. But doing a pull or merge _should_ update the working tree to match the committed versions. It does with file data, so why not update the submodules? Especially if the submodule revision matched the committed version -before- the pull. Why are we forced into using 'git submodule update'? - Steven -- 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