Submodule-modes: Distinguish between update modes and update targets

[git-submod-enhancements.wiki.git] / Home.textile

diff --git a/Home.textile b/Home.textile
index 50523a89525de4810c2c83a082d837f34251e24b..8882dd002c532210aa295d2701d09b84cbac8257 100644 (file)
--- a/Home.textile
+++ b/Home.textile
@@ -5,7 +5,6 @@ As Dscho put it, submodules are the "neglected ugly duckling" of git. Time to ch
 *Issues currently being worked on*
 
 * [[Recursive submodule checkout]]: teach all work tree manipulating commands to update the submodule work trees according to the commit recorded in the superproject.
-* Teach @git mv@ to not only move the gitlink and the work tree but also update core.worktree and the gitfile
 * Teach @git fetch@ to also fetch commits for submodule not currently in the work tree into .git/modules/<name>
 
 *Issues still to be tackled*
@@ -14,6 +13,7 @@ As Dscho put it, submodules are the "neglected ugly duckling" of git. Time to ch
 * Add a git-config aware merge driver and make it the default for .gitmodules
 * Attempt a 3-way merge when @git mv@, @git rm@ or @git submodule add@ want to change a .gitmodules file which has unstaged changes
 * Add configuration options (global, per repo and per submodule) to set the default of @git push --recurse-submodules@
+* Add a tutorial explaining the different use cases and the configuration settings which suit them.
 * Add an option to @git submodule add@ to move the .git directory of a local repository to be added as submodule into the .git/modules directory of the superproject
 * Teach @grep@ the @--recursive@ option
 * 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)