For a complete description of this bug, see
http://stackoverflow.com/questions/32782382/git-moving-submodules-recursively-nested-submodules/32924692?noredirect=1#comment53760394_32924692
--
Bart Bogaerts
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of
://stackoverflow.com/q/32782382/2274140
--
Bart Bogaerts
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
bartb@EB-Latitude-E5450 ~/Documents/papers $
2016-06-27 19:57 GMT+03:00 Stefan Beller :
> On Sun, Jun 26, 2016 at 11:01 PM, Bart Bogaerts
> wrote:
>> With a repo structured as follows
>>
>> main-files
>> |- submod
>> |- subsubmodule
>>
>> git mv
+ git status &&
> + git config -f .gitmodules submodule.deep/outer_sub.path >actual &&
> + echo "outer_sub_moved" >expect &&
> + test_cmp actual expect
> +'
> +
> +test_expect_success 'moving back th
a -m "added submod"
) &&
#create the directory to test in
(
mkdir testdir &&
cd testdir &&
git init &&
git submodule add ../repo2 &&
git commit -m "added full structure" &&
#important to initialise .git files!
git submodu
5 matches
Mail list logo