From 755f9935d0346b0fb9e676d1033f980d7afe5619 Mon Sep 17 00:00:00 2001 From: Jens Lehmann Date: Fri, 10 May 2013 02:39:30 -0700 Subject: [PATCH] Updated Recursive submodule checkout (textile) --- Recursive-submodule-checkout.textile | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/Recursive-submodule-checkout.textile b/Recursive-submodule-checkout.textile index 6e77498..c4aa1bf 100644 --- a/Recursive-submodule-checkout.textile +++ b/Recursive-submodule-checkout.textile @@ -1,7 +1,9 @@ +This effort is about teaching @am@, @bisect@, @checkout@, @checkout-index@, @cherry-pick@, @merge@, @pull@, @read-tree@, @rebase@, @reset@ & @stash@ to recursively update submodule work trees according to the commit recorded in the superproject (which gets rid of having to run "git submodule update" every time something changes). + You find the current state of this series in the [[recusive_submodule_update|https://github.com/jlehmann/git-submod-enhancements/tree/recursive_submodule_checkout]] branch in this repo. **Be warned: the code is still experimental and might damage your data!** -Especially when removing a submodule on checkout all untracked files inside it will be lost! (and it'll stay that way until the discussed ignored-but-precious attribute is implemented in Git) +Especially when removing a submodule on checkout all ignored untracked files inside it will be lost! (and it'll stay that way until the discussed ignored-but-precious attribute is implemented in Git) Having said that, I already use this code for quite some time at my dayjob and it's working fine for me. -- 2.26.2