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

[PATCH] gitmodules: clarify what history depth a shallow clone has

From
Sebastian Schuberth <sschuberth@gmail.com>
Date
Apr 19, 2017, 07:56 UTC
Message-ID
<0102015b853681c6-2fb6f9ce-28dc-4ca8-82de-d5fbff10d3af-000000@eu-west-1.amazonses.com>
Signed-off-by: Sebastian Schuberth <sschuberth@gmail.com>
---
 Documentation/gitmodules.txt | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/gitmodules.txt b/Documentation/gitmodules.txt
index 8f7c50f..6f39f24 100644
--- a/Documentation/gitmodules.txt
+++ b/Documentation/gitmodules.txt
@@ -84,8 +84,8 @@ submodule.<name>.ignore::
 
 submodule.<name>.shallow::
 	When set to true, a clone of this submodule will be performed as a
-	shallow clone unless the user explicitly asks for a non-shallow
-	clone.
+	shallow clone (with a history depth of 1) unless the user explicitly
+	asks for a non-shallow clone.
 
 
 EXAMPLES

--
https://github.com/git/git/pull/347
Next: Stefan Beller
Message 1 of 2 in “gitmodules: clarify what history depth a shallow clone has”
  1. gitmodules: clarify what history depth a shallow clone hasSebastian Schuberth, Apr 19, 2017
  2. Stefan BellerApr 19, 2017

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.