19 Dec
2013
19 Dec
'13
8:34 p.m.
On 12/19/2013 05:55 PM, John Maddock wrote:
"git submodule update" is subsequently required to actually change the contents of the submodule working spaces to contain those versions. It's probably a separate step because that makes it easier to deal with conflicts in specific submodules that were locally modified.
I assume "git submodule update" is done at the superproject level. But as other have said, this puts everything back into detached state so that one needs to checkout whatever branches one was working on before again. Ugh !
Ugh indeed.
What happens to uncommitted changes in that case?
I don't think there is reason to worry. Git is very cautious not to loose data for you. -- Bjørn