aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorBoris Kolpackov <boris@codesynthesis.com>2015-11-30 14:41:46 +0200
committerBoris Kolpackov <boris@codesynthesis.com>2015-11-30 14:41:46 +0200
commitba02affe2a5721bc1290b88aed8b4d7b8a48ee15 (patch)
tree0baf2ae2cd7aff53afe9620877607f2045eb6f8d
parent30a2a9048ca39101a7d1699d5a4497acb43fb185 (diff)
Add note on submodule "mental model"
-rw-r--r--cheatsheet.txt8
1 files changed, 8 insertions, 0 deletions
diff --git a/cheatsheet.txt b/cheatsheet.txt
index 92bc1e5..bcb5e4c 100644
--- a/cheatsheet.txt
+++ b/cheatsheet.txt
@@ -179,6 +179,14 @@ History Cleanup
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
+ 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 status.submoduleSummary true
git config --global diff.submodule log