Hi! I wonder what if there is any reason for not making the submodule management much more easier for the user.
I mean, for example. if there is some submodule on a git repository, the default behaviour should be to make it available when you clone the repository, and update it when is updated. Maybe there is a use case for not perform those actions, but in that case, the submodule should be able to be configured (in the git repo config) and behave as I descripted. Were the requirements are described and can be discussed? I think that submodule functionality can be much more used if were more transparent for the users. (Our use case is to maintain the .mvn folder in a single repository, with a setup compatible for CI and local of all our repositories) Best regards! -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/git-users/ca6910f6-0e14-4deb-b7ec-92eec4c3bdb9n%40googlegroups.com.
