3 ms·
This might be because it's ambiguous which submodules you want to update if you have nested submodules. In other words, git knows "exactly where that is" by se
by raylu 14y ago
This might be because it's ambiguous which submodules you want to update if you have nested submodules.
In other words, git knows "exactly where that is" by searching parent directories until it sees a ".git". Unfortunately, submodules also have ".git" in them since they're full git repositories themselves.
git submodules are not the nicest part of git, unfortunately.
- hesselink 14y agoOK, so it wouldn't work if you're in a submodule. It could print a warning if there are no submodules. But if would still work perfectly fine in the majority of the cases. For those also annoyed, I use this git alias, which does what I want: sup = !sh -c 'cd `git rev-parse --show-toplevel` && git submodule update --init' -