aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorRalf Wildenhues <Ralf.Wildenhues@gmx.de>2007-11-01 09:46:02 +0100
committerJunio C Hamano <gitster@pobox.com>2007-11-01 15:14:38 -0700
commitd9d10bb8549ca0353d13298e372c1c87bcc530ef (patch)
treea5a8329553165b4f95f8b4bcf26a9b28b257e791
parent1e3a2eb667256716e101707f4da7179da2ba3c65 (diff)
downloadgit-d9d10bb8549ca0353d13298e372c1c87bcc530ef.tar.gz
git-d9d10bb8549ca0353d13298e372c1c87bcc530ef.tar.xz
git-clone.txt: Improve --depth description.
Avoid abbreviation 'revs', improve the language a bit. Signed-off-by: Junio C Hamano <gitster@pobox.com>
-rw-r--r--Documentation/git-clone.txt6
1 files changed, 3 insertions, 3 deletions
diff --git a/Documentation/git-clone.txt b/Documentation/git-clone.txt
index 253f4f03c..cca14d6b5 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>::