summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJunio C Hamano <gitster@pobox.com>2013-07-18 12:59:59 -0700
committerJunio C Hamano <gitster@pobox.com>2013-07-18 13:00:00 -0700
commit30f7ad08e69561e638a0e95345b74aa2806331dc (patch)
treecf8129262f76b10d484c4eb7dd23f1ed1d24de77
parentcbc7fdf81dee94333f11e775ab47b7e7b35ea81c (diff)
parent5333f2afc4f5c6365845b25ffc22a91379b84c58 (diff)
downloadgit-30f7ad08e69561e638a0e95345b74aa2806331dc.tar.gz
Merge branch 'jc/revert-clone-doc-update-for-push-from-shallow'
* jc/revert-clone-doc-update-for-push-from-shallow: Revert "git-clone.txt: remove the restriction on pushing from a shallow clone"
-rw-r--r--Documentation/git-clone.txt12
1 files changed, 5 insertions, 7 deletions
diff --git a/Documentation/git-clone.txt b/Documentation/git-clone.txt
index 85769b884e..450f158779 100644
--- a/Documentation/git-clone.txt
+++ b/Documentation/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,