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

[PATCH] submodule: indicate that 'submodule.recurse' doesn't apply to clone

From
BWBrandon Williams <bmwill@google.com>
Date
Feb 20, 2018, 20:29 UTC
Message-ID
<20180220202922.220568-1-bmwill@google.com>

Update the documentation for the 'submodule.recurse' config to identify that the clone command does not respect it.

Signed-off-by: Brandon Williams <bmwill@google.com>
---
 Documentation/config.txt | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/Documentation/config.txt b/Documentation/config.txt
index f57e9cf10..59ff29d7a 100644
--- a/Documentation/config.txt
+++ b/Documentation/config.txt
@@ -3210,7 +3210,8 @@ submodule.active::
 
 submodule.recurse::
 	Specifies if commands recurse into submodules by default. This
-	applies to all commands that have a `--recurse-submodules` option.
+	applies to all commands that have a `--recurse-submodules` option,
+	except `clone`.
 	Defaults to false.
 
 submodule.fetchJobs::
-- 
2.16.1.291.g4437f3f132-goog
Next: Junio C Hamano
Message 1 of 2 in “submodule: indicate that 'submodule.recurse' doesn't apply to clone”
  1. submodule: indicate that 'submodule.recurse' doesn't apply to cloneBrandon Williams, Feb 20, 2018
  2. Junio C HamanoFeb 21, 2018

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.