On Thu, Aug 17, 2017 at 3:34 AM, Heiko Voigt <hvo...@hvoigt.net> wrote: > When using git-mv with a submodule it will detect that and update the > paths for its configurations (.gitmodules, worktree and gitfile). This > does not work for nested submodules where a user renames the root > submodule. > > We discovered this fact when working on on-demand fetch for renamed > submodules. Lets add a test to document. > > Signed-off-by: Heiko Voigt <hvo...@hvoigt.net> > --- > t/t7001-mv.sh | 9 +++++++++ > 1 file changed, 9 insertions(+) > > diff --git a/t/t7001-mv.sh b/t/t7001-mv.sh > index e365d1f..39f8aed 100755 > --- a/t/t7001-mv.sh > +++ b/t/t7001-mv.sh > @@ -491,4 +491,13 @@ test_expect_success 'moving a submodule in nested > directories' ' > test_cmp actual expect > ' > > +test_expect_failure 'moving nested submodules' ' > + git commit -am "cleanup commit" && > + git submodule add ./. sub_nested &&
If possible, I would avoid adding the repo itself as a submodule as it is unrealistic in the wild. While it may be ok for the test here, later down the road other tests making use of it it may become an issue with the URL of the submodule. > + git commit -m "add sub_nested" && > + git submodule update --init --recursive && > + git mv sub_nested sub_nested_moved && > + git status > +' > + > test_done > -- > 2.0.0.274.g6b2cd91 >
