Re: Submodule regression in 2.14?

From: Stefan Beller <sbeller@google.com>
Date: Aug 18, 2017, 17:16 UTC
Message-ID: <CAGZ79kaC-rtfp-AMdpkpCycgk568eU2y-JDGwdoSK_E=oUJo-w@mail.gmail.com>
In-Reply-To: <D784E926-9FC7-4508-9632-225138679CDF@gmail.com>

> In the past "submodule.<name>.update=none" was an easy way
> to selectively disable certain Submodules.
>
> How would I do this with Git 2.14?

    submodule.<name>.active = false

> My gut feeling is that all commands should respect the
> "submodule.<name>.update=none" setting.

Well my gut feeling was that the "update" part of the name reponds to the subcommand, not the generic action.

For example when you set update=none, git-status, recursive git-diff still reported the submodule.

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