Am 18.02.2012 22:27, schrieb Adrian Cornish: > If I add a submodule to a branch and then switch branches, git > checkout warns it cannot > remove the submodule. If I then issue a git clean - it says it removes > the submodule but > in fact does nothing at all. Is this a bug or expected behaviour. Right this is just how things work. I won't call it expected behavior, as some users (like you) would expect to see the submodule be removed (while others are used to the current behavior that submodule work trees are never touched). But one of last years GSoC projects took first steps into the direction of safely removing submodules (without losing any history). I have experimental code at my Github repo [1] to update submodule work trees along with the superproject, but polishing that for inclusion into mainline will still take some time. [1] https://github.com/jlehmann/git-submod-enhancements -- 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