Heiko Voigt <hvoigt@xxxxxxxxxx> writes: > If a submodule is used to seperate some bigger parts of a project into > an optional directory it is helpful to not clone/update them by default. Sorry if I am slow, but I do not get this. I thought unless you say "submodule init" once, a submodule you are not interested in should not be cloned nor updated at all. If that is not the case, isn't it a bug to be fixed without a new configuration variable that fixes it only when it is set? > We have been talking about loose submodules for some time: Also before introducing a new terminology "loose submodule", please define it somewhere. It feels confusing to me that a normal submodule, which shouldn't be auto-cloned nor auto-updated without "submodule init", needs to be called by a name other than simply a "submodule" but with an adjuctive "loose submodule". -- 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