From 68f9c25a76cb7794d9498bb2923eba997b099cc6 Mon Sep 17 00:00:00 2001 From: Boris Kolpackov Date: Sat, 30 Jan 2016 09:14:47 +0200 Subject: Update submodules cheatsheet --- cheatsheet.txt | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) (limited to 'cheatsheet.txt') 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 -- cgit v1.1