31 Jul
2017
31 Jul
'17
6:16 p.m.
On 07/31/2017 02:09 PM, Christian Rebischke wrote:
Do I really need to do this? Won't the 'git submodule update' command choose the correct commit?
May somebody else correct me, but I don't think so. `git submodule update` will just update to the HEAD of the sub repository. And we want stable builds. Therefore it's important to pin the software at a specific commit and it's dependencies, too.
You're both right and wrong. "$srcdir/$submodulename" will be at origin/master, but `git submodule update` in the primary repo will completely ignore that clone altogether and just cares about the git objects which it uses in yet another clone. -- Eli Schwartz