Denton Liu <liu.denton@xxxxxxxxx> writes: > I think that the problem is that it's a common enough use-case but not > common enough that people often forget to "sync" after editing the > .gitmodules. Which means that far from deprecating "sync", we should strive for imprinting the need for the use of the subcommand deeper in users' minds. I wonder if it makes sense to make sure that .gitmodules file starts with something like # Note that after updating this file, you may want to # run "git submodule sync" so that the URL for the remote # repository etc. are propagated down. when we create it (via, say "git submodule add")? Or alternatively, warn the users when "git status" notices a local modification, or something along that line?