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

[PATCH] git-clone.txt: Improve --depth description.

From
RWRalf Wildenhues <ralf.wildenhues@gmx.de>
Date
Nov 1, 2007, 08:46 UTC
Message-ID
<20071101084602.GB4934@ins.uni-bonn.de>
Avoid abbreviation 'revs', improve the language a bit.
---
 Documentation/git-clone.txt |    6 +++---
 1 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/Documentation/git-clone.txt b/Documentation/git-clone.txt
index 253f4f0..cca14d6 100644
--- a/Documentation/git-clone.txt
+++ b/Documentation/git-clone.txt
@@ -111,11 +111,11 @@ OPTIONS
 
 --depth <depth>::
 	Create a 'shallow' clone with a history truncated to the
-	specified number of revs.  A shallow repository has
+	specified number of revisions.  A shallow repository has a
 	number of limitations (you cannot clone or fetch from
 	it, nor push from nor into it), but is adequate if you
-	want to only look at near the tip of a large project
-	with a long history, and would want to send in a fixes
+	are only interested in the recent history of a large project
+	with a long history, and would want to send in fixes
 	as patches.
 
 <repository>::
-- 
1.5.3.1.522.g85b0
Message 1 of 1 in “git-clone.txt: Improve --depth description.”
  1. git-clone.txt: Improve --depth description.Ralf Wildenhues, Nov 1, 2007

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.