Am 29.08.2010 19:29, schrieb Ævar Arnfjörð Bjarmason: > However I wonder if we're going to make --recursive the > default for pull/fetch whether it shouldn't be made the default for > clone while we're at it. Hm, while that would work for me (and for you obviously ;-), it wouldn't make sense for other use cases where submodules are used as a kind of sparse checkout (and then some of them are never meant to be checked out, at least by some users). I don't think recursive fetch would hurt there, as that only affects already populated submodules, so turning that on by default sounds safe. After finishing the recursive checkout of populated submodules one of my next goals is to teach clone to recurse too, but only for those submodules where this is wanted (aka configured via .gitmodules). -- 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