summaryrefslogtreecommitdiffstats
path: root/git-clone.html
diff options
context:
space:
mode:
authorJunio C Hamano <gitster@pobox.com>2013-07-12 15:47:46 -0700
committerJunio C Hamano <gitster@pobox.com>2013-07-12 15:47:46 -0700
commit8401f142a88980c91f3af6f06199e5579c9143c6 (patch)
tree3bce834aaee41a0b122eb45ab2ce5fb26a747df8 /git-clone.html
parent5865559b9be66a59108c9f38b1e9f4d91201ebc6 (diff)
downloadgit-htmldocs-8401f142a88980c91f3af6f06199e5579c9143c6.tar.gz
Autogenerated HTML docs for v1.8.3.2-804-g0da7a
Diffstat (limited to 'git-clone.html')
-rw-r--r--git-clone.html13
1 files changed, 7 insertions, 6 deletions
diff --git a/git-clone.html b/git-clone.html
index 3c8a73fae..78d7d33f6 100644
--- a/git-clone.html
+++ b/git-clone.html
@@ -1013,12 +1013,13 @@ objects from the source repository into a pack in the cloned repository.</p></di
<p>
Create a <em>shallow</em> 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.
</p>
+<div class="paragraph"><p>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.</p></div>
</dd>
<dt class="hdlist1">
--[no-]single-branch
@@ -1289,7 +1290,7 @@ Create a bare repository to publish your changes to the public:
<div id="footnotes"><hr /></div>
<div id="footer">
<div id="footer-text">
-Last updated 2013-07-01 14:29:27 PDT
+Last updated 2013-07-12 15:46:35 PDT
</div>
</div>
</body>