From 351dd63b6908784507b75c01d4d17b36d2bd199e Mon Sep 17 00:00:00 2001 From: jlehmann Date: Sun, 14 Oct 2012 12:18:55 -0700 Subject: [PATCH] Updated Home (textile) --- Home.textile | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/Home.textile b/Home.textile index 11178d8..9045c4f 100644 --- a/Home.textile +++ b/Home.textile @@ -6,7 +6,7 @@ As Dscho put it, submodules are the "neglected ugly duckling" of git. Time to ch * Let @am@, @bisect@, @checkout@, @checkout-index@, @cherry-pick@, @merge@, @pull@, @read-tree@, @rebase@, @reset@ & @stash@ work recursively on submodules (in progress) * Teach @grep@ the @--recursive@ option -* Add means to specify which submodules shall be populated on clone +* Add means to specify which submodules shall be populated on clone (which I'd like to implement by teaching @git fetch@ to create submodule repos in .git/modules, recursive checkout will then do the rest) * Showing that a submodule has a HEAD not on any branch in @git status@ * @gitk@: Add popup menu for submodules to see the detailed history of changes * Teach @git prune@ the @--recurse-submodules@ option (and maybe honour the same default and options @git fetch@ uses) @@ -19,9 +19,9 @@ As Dscho put it, submodules are the "neglected ugly duckling" of git. Time to ch *Submodule related bugs to fix* +* @git fetch@ doesn't fetch referenced commits after a submodule rename * Cherry picking across submodule creation fails even if the cherry pick doesn't touch any file in the submodules path * @git submodule add@ doesn't record the URL in .git/config when the submodule path doesn't exist. -* @git rebase --continue@ won't work if the commit only contains submodule changes. *Issues already solved and merged into Junio's Repo:* @@ -47,4 +47,7 @@ As Dscho put it, submodules are the "neglected ugly duckling" of git. Time to ch ** @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) \ No newline at end of file +** 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 -- 2.26.2