Jens Lehmann <Jens.Lehmann@xxxxxx> writes: > It might surprise people. E.g. when their old scripts don't work anymore as > they did before because a submodule won't be populated or updated in the work > tree even though it is present in .git/config. So I agree that this should be > documented in the release notes so people can check if their expectations are > still met. Worse yet, their custom old scripts that they use to update submodules in their repository, if properly written, assume that anything registered in the .git/config file as [submodule "foo"] _must_ be populated, but they can no longer assume that and now has to look at submodule.foo.update and if it notices the variable is set to "none" leave the submodule repository alone. Having "submodule.foo" registered in the .git/config file alone used to mean the user is interested in "foo" submodule and wants to have a checkout for it, now it does not necessarily mean that. That is definitely a huge semantics change. -- 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