Stefan Beller <sbeller@xxxxxxxxxx> writes: > Are you saying this might be a design mistake and > the .update ought to be respected by all the other > commands? For example > git reset --recurse-submodules > should ignore the .update= none? I have been under the impression that that has been the traditional desire of what .update ought to mean. I personally do not have a strong opinion---at least not yet. > When designing these new recursive submodule functionality > outside the "submodule" command, I'd want submodules > to behave as much as possible like trees. I think that is sensible as long as the user does not explicitly say "this and that submodule behave differently" by giving configuration variables. Perhaps .update is one of those that should countermand the default behaviour of "--recurse-submodules"?
