Submodule regression in 2.14?

From: Lars Schneider <larsxschneider@gmail.com>
Date: Aug 16, 2017, 18:35 UTC
Message-ID: <4283F0B0-BC1C-4ED1-8126-7E512D84484B@gmail.com>

Hi,

I think we discovered a regression in Git 2.14.1 today. It looks like as if "git submodule update --init --recursive" removes the "skip submodules" config.

Consider the following steps:

    git clone https://server/repo.git
    cd repo
    git config --local submodule.some/other/repo.update none
    git submodule update --init --recursive
    git pull --recurse-submodules

With Git 2.14 the last "git pull" will clone the "some/other/repo" submodule. This did not happen with Git 2.13.

Bug or feature? I don't have anymore time for Git today. I am happy to provide a proper test case tomorrow, though.

Cheers, Lars

$ 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.