From c7fb4a907673b5c22382b8841c3401ed5b615615 Mon Sep 17 00:00:00 2001 From: jlehmann Date: Thu, 2 Feb 2012 03:19:20 -0800 Subject: [PATCH] Updated Home (textile) --- Home.textile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Home.textile b/Home.textile index 692df1a..e8179fe 100644 --- a/Home.textile +++ b/Home.textile @@ -45,6 +45,6 @@ As Dscho put it, submodules are the "neglected ugly duckling" of git. Time to ch ** 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 (part of Frederik Gustafsson's 2011 GSoC project) -* Since git 1.7.7: +* Since git 1.7.8: ** 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 (part of Frederik Gustafsson's 2011 GSoC project) \ No newline at end of file -- 2.26.2