git/list[1] front-page[2] threads[3] people[4] search[5] about
 

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

From
Rron <ronazek@protonmail.com>
Date
Apr 11, 2019, 02:36 UTC
Message-ID
<Otial29UjnjP-PuGN9Mwnd8k4q8Alof6wWOxFqYv_mXpNbumrljWGN44RvNZYIkC-in7KSXzjFjbceYglTW4iACRcven7CyHUUSUcPCWbL4=@protonmail.com>
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.
Next: Ron
Message 1 of 3 in “Local Config File: Submodule initialization looks broken with the --recurse-submodules option when cloning a repository”
  1. ronApr 11, 2019
  2. RonOct 14, 2019
  3. RonOct 15, 2019

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.