summaryrefslogtreecommitdiffstats
path: root/git-clone.txt
diff options
context:
space:
mode:
authorJunio C Hamano <gitster@pobox.com>2013-07-18 17:36:45 -0700
committerJunio C Hamano <gitster@pobox.com>2013-07-18 17:36:45 -0700
commit0f578a770096493285b13bd2856091778a8579aa (patch)
tree8dd092ad641d53207f93b8df3ba4f7c07d0d0cd4 /git-clone.txt
parent24b683581d6d454d453d86f2e1ab7401dcb8faea (diff)
downloadgit-htmldocs-0f578a770096493285b13bd2856091778a8579aa.tar.gz
Autogenerated HTML docs for v1.8.3.3-797-gb72c6
Diffstat (limited to 'git-clone.txt')
-rw-r--r--git-clone.txt12
1 files changed, 5 insertions, 7 deletions
diff --git a/git-clone.txt b/git-clone.txt
index 85769b884..450f15877 100644
--- a/git-clone.txt
+++ b/git-clone.txt
@@ -182,13 +182,11 @@ objects from the source repository into a pack in the cloned repository.
--depth <depth>::
Create a 'shallow' clone with a history truncated to the
specified number of revisions. A shallow repository has a
- number of limitations (you cannot clone or fetch from it, nor
- push into it), but is adequate if you are only interested in
- the recent history of a large project with a long history.
-+
-Pushing from a shallow clone should be avoided if the git version on
-the receiver end is older than v1.7.10, or any other git
-implementation that does not perform connectivity check.
+ number of limitations (you cannot clone or fetch from
+ it, nor push from nor into it), but is adequate if you
+ are only interested in the recent history of a large project
+ with a long history, and would want to send in fixes
+ as patches.
--[no-]single-branch::
Clone only the history leading to the tip of a single branch,