diff options
| author | Junio C Hamano <gitster@pobox.com> | 2013-07-12 15:47:46 -0700 |
|---|---|---|
| committer | Junio C Hamano <gitster@pobox.com> | 2013-07-12 15:47:46 -0700 |
| commit | 8401f142a88980c91f3af6f06199e5579c9143c6 (patch) | |
| tree | 3bce834aaee41a0b122eb45ab2ce5fb26a747df8 /git-clone.txt | |
| parent | 5865559b9be66a59108c9f38b1e9f4d91201ebc6 (diff) | |
| download | git-htmldocs-8401f142a88980c91f3af6f06199e5579c9143c6.tar.gz | |
Autogenerated HTML docs for v1.8.3.2-804-g0da7a
Diffstat (limited to 'git-clone.txt')
| -rw-r--r-- | git-clone.txt | 12 |
1 files changed, 7 insertions, 5 deletions
diff --git a/git-clone.txt b/git-clone.txt index 450f15877..85769b884 100644 --- a/git-clone.txt +++ b/git-clone.txt @@ -182,11 +182,13 @@ 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. + 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. --[no-]single-branch:: Clone only the history leading to the tip of a single branch, |