summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorNguyễn Thái Ngọc Duy <pclouds@gmail.com>2013-12-05 20:02:55 +0700
committerJunio C Hamano <gitster@pobox.com>2013-12-10 16:14:19 -0800
commit82fba2b9d39163a0c9b7a3a2f35964cbc039e1aa (patch)
treef502fa144a325c536c45ee7ec1ffa27c45d3d6e1
parenteab3296c7e5c99f559818357e70eeae09c24ac99 (diff)
downloadgit-82fba2b9d39163a0c9b7a3a2f35964cbc039e1aa.tar.gz
git-clone.txt: remove shallow clone limitations
Now that git supports data transfer from or to a shallow clone, these limitations are not true anymore. Signed-off-by: Nguyễn Thái Ngọc Duy <pclouds@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
-rw-r--r--Documentation/git-clone.txt7
1 files changed, 1 insertions, 6 deletions
diff --git a/Documentation/git-clone.txt b/Documentation/git-clone.txt
index 450f158779..49878570bf 100644
--- a/Documentation/git-clone.txt
+++ b/Documentation/git-clone.txt
@@ -181,12 +181,7 @@ 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 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.
+ specified number of revisions.
--[no-]single-branch::
Clone only the history leading to the tip of a single branch,