Re: Local Config File: Submodule initialization looks broken with the --recurse-submodules option when cloning a repository

From: Ron <ronazek@protonmail.com>
Date: Oct 14, 2019, 01:35 UTC
Message-ID: <ZkLbpInDB0A-uWL3lVcy67PplIX56Pr7qakiHnXnP4OInRFs20ZPH3wDZl-LNoCNRv-_4HlTwa9LLkrWjdVFPshEi-JXVAhHwsLdp2ivJew=@protonmail.com>
In-Reply-To: <Otial29UjnjP-PuGN9Mwnd8k4q8Alof6wWOxFqYv_mXpNbumrljWGN44RvNZYIkC-in7KSXzjFjbceYglTW4iACRcven7CyHUUSUcPCWbL4=@protonmail.com>

Show 25 quoted lines

> Initially reported for GFW on version 2.20.1, I have tested with Linux Mint Mate 19.1 Tessa which by default uses git version 2.17.1
>
> It produces a config file with the relevant submodule entries looking like this:
>
> -----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> [submodule]
> active = .
>
> [submodule "Submodule/Path"]
> url = https://github.com/organization/submodule.git
>
> ---------------------------------------------------------------------------------------------------------
>
> Instead of that, which is produced by manually initializing a submodule anytime after cloning:
>
> -------------------------------------------------------------------------------------------------
>
> [submodule "Submodule/Path"]
> active = true
> url = https://github.com/organization/submodule.git
>
> -----------------------------------------------------------------------------------------------
>
> Sent with ProtonMail Secure Email.

I've got someone to test this with the latest 2.23.0 version on archlinux.

It is still happening:

git clone --depth=1 --recurse-submodules --origin upstream https://github.com/git-for-windows/git; git -C git config --get submodule.active expected true, got .

Anything more I need to add to help this get solved?

Sent with ProtonMail Secure Email.