From 434dad3104cdd37f03cd1e0899a4f1547e70cf81 Mon Sep 17 00:00:00 2001 From: jlehmann Date: Sun, 10 Feb 2013 12:28:23 -0800 Subject: [PATCH] Updated Home (textile) --- Home.textile | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/Home.textile b/Home.textile index a1e42f9..f756be7 100644 --- a/Home.textile +++ b/Home.textile @@ -45,10 +45,13 @@ As Dscho put it, submodules are the "neglected ugly duckling" of git. Time to ch * Since git 1.7.5: ** @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) +** @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.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) * Since git 1.7.11: ** @git rebase --continue@ works if the commit only contains submodule changes. ** @git push@ learned the --recurse-submodules=on-demand option +* Since git 1.8.1: +** @git rm@ removes submodules from index and work tree (unless they contain a .git directory) +** @git submodule add@ learned the @--name@ option so the user can choose the name for a submodule (e.g. when its name clashes with that of a submodule which was present at the same path earlier in history but was removed). \ No newline at end of file -- 2.26.2