| 36 | | The {{{git submodule update}}} switches submodules back to the detached state if the submodule is already at the commit specified by the super-project for that submodule. Otherwise the submodule stays at the commit (and branch) it is already on. |
| 37 | | |
| 38 | | To get more information about submodules, do: |
| | 36 | The {{{git submodule update}}} may switch submodules back to the detached state, depending on the working copy's exact situation. |
| | 37 | |
| | 38 | || '''Working copy before {{{git submodule update}}}''' || '''Working copy after {{{git submodule update}}}''' || |
| | 39 | || super-project status <<<Changes not staged for commit: ... modified: subproject (new commits)>>>. Subproject is detached, at 1 commit behind super-project origin Head, nothing to commit || super-project status <<<nothing to commit>>>. Subproject is detached, at super-project origin Head commit, nothing to commit || |
| | 40 | |
| | 41 | |
| | 42 | Tests run on git version 1.8.4.msysgit.0 |
| | 43 | |
| | 44 | To get more information about submodules: |
