diff options
| author | Boris Kolpackov <boris@codesynthesis.com> | 2016-01-30 09:14:47 +0200 |
|---|---|---|
| committer | Boris Kolpackov <boris@codesynthesis.com> | 2016-01-30 09:14:47 +0200 |
| commit | 68f9c25a76cb7794d9498bb2923eba997b099cc6 (patch) | |
| tree | fb24023e269508c093604f3f56c6e551be59ce85 /cheatsheet.txt | |
| parent | e65dc35e2e4ec2f6c88bdba6067d22d7f3de3ffd (diff) | |
Update submodules cheatsheet
Diffstat (limited to 'cheatsheet.txt')
| -rw-r--r-- | cheatsheet.txt | 5 |
1 files changed, 3 insertions, 2 deletions
diff --git a/cheatsheet.txt b/cheatsheet.txt index bee3cf9..72727dc 100644 --- a/cheatsheet.txt +++ b/cheatsheet.txt @@ -194,11 +194,12 @@ Submodules Think of a submodule as a pointer to a specific commit (as opposed to something "latest") in another project. Moving this pointer to another commit is an explicit change to the containing project that - we must perform and then commit. In many situations this pointer - will be "dangling", that is, the actual files corresponding to the + we must perform and then commit. In many situations this pointer will + be left "dangling", that is, the actual files corresponding to the commit won't be checked out unless we run an extra command or pass an extra option to make git do so. + git config --global fetch.recurseSubmodules true git config --global status.submoduleSummary true git config --global diff.submodule log |