Re: [PATCH v3 0/4] clone: update submodule.recurse in config when using --recurse-submodule

From: Junio C Hamano <gitster@pobox.com>
Date: Aug 3, 2021, 22:41 UTC
Message-ID: <xmqq5ywmtalh.fsf@gitster.g>
In-Reply-To: <pull.1006.v3.git.1627946590.gitgitgadget@gmail.com>

"Mahi Kolla via GitGitGadget" <gitgitgadget@gmail.com> writes:

> When running 'git clone --recurse-submodules', developers expect various
> other commands such as 'pull' and 'checkout' to also run recursively into
> submodules.

Some developers might, but "developers expect" as if we speak for everybody is a bold statement to make that needs to be substantiated, I would think. Is this something easy to make opt-in, e.g. "git clone --recurse-submodules=sticky" or something?

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