From 9cf7695f095f88395874ea9a8288dfd62701bd08 Mon Sep 17 00:00:00 2001 From: jlehmann Date: Tue, 17 Jan 2012 13:43:55 -0800 Subject: [PATCH] Updated Home (textile) --- Home.textile | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/Home.textile b/Home.textile index 921f891..6f94dc5 100644 --- a/Home.textile +++ b/Home.textile @@ -44,4 +44,9 @@ As Dscho put it, submodules are the "neglected ugly duckling" of git. Time to ch * Since git 1.7.4: ** Recursive fetching of submodules can be enabled via command line option or configuration. * Since git 1.7.5: -** fetch runs recursively on submodules by default when new commits have been recorded for them in the superproject \ No newline at end of file +** fetch runs recursively on submodules by default when new commits have been recorded for them in the superproject +* Since git 1.7.7: +** git push learned the --recurse-submodules=check option which errors out when trying to push a superproject commit where the submodule changes are not pushed +* Since git 1.7.7: +** The "update" option learned the value "none" which disables "submodule init" and "submodule update" +** The git directory of a newly cloned submodule is stored in the .git directory of the superproject, the submodules work tree contains only a gitfile. This is the first step towards recursive checkout, as it enables us to remove a submodule directory. \ No newline at end of file -- 2.26.2