diff options
author | Junio C Hamano <gitster@pobox.com> | 2013-07-18 17:36:45 -0700 |
---|---|---|
committer | Junio C Hamano <gitster@pobox.com> | 2013-07-18 17:36:45 -0700 |
commit | 0f578a770096493285b13bd2856091778a8579aa (patch) | |
tree | 8dd092ad641d53207f93b8df3ba4f7c07d0d0cd4 /git-clone.html | |
parent | 24b683581d6d454d453d86f2e1ab7401dcb8faea (diff) | |
download | git-htmldocs-0f578a770096493285b13bd2856091778a8579aa.tar.gz |
Autogenerated HTML docs for v1.8.3.3-797-gb72c6
Diffstat (limited to 'git-clone.html')
-rw-r--r-- | git-clone.html | 13 |
1 files changed, 6 insertions, 7 deletions
diff --git a/git-clone.html b/git-clone.html index 78d7d33f6..230a84484 100644 --- a/git-clone.html +++ b/git-clone.html @@ -1013,13 +1013,12 @@ 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 into it), but is adequate if you are only interested in
- the recent history of a large project with a long history.
+ 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.
</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
@@ -1290,7 +1289,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-12 15:46:35 PDT
+Last updated 2013-07-18 17:36:26 PDT
</div>
</div>
</body>
|