git-clone.txt: remove the restriction on pushing from a shallow clone
The document says one cannot push from a shallow clone. But that is not true (maybe it was at some point in the past). The client does not stop such a push nor does it give any indication to the receiver that this is a shallow push. If the receiver accepts it, it's in. Since 52fed6e (receive-pack: check connectivity before concluding "git push" - 2011-09-02), receive-pack is prepared to deal with broken push, a shallow push can't cause any corruption. Update the document to reflect that. Signed-off-by: Nguyễn Thái Ngọc Duy <pclouds@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Nguyễn Thái Ngọc Duy committed
Jul 12, 2013 at 12:37 UTC
dacd2bcc414e0b7aac36aaa400da0a743c4741cc
1 file changed
+7
-5
Documentation/git-clone.txt
+7
-5
@@ -182,11 +182,13 @@ objects from the source repository into a pack in the cloned repository.
182
--depth <depth>::
183
Create a 'shallow' clone with a history truncated to the
184
specified number of revisions. A shallow repository has a
185
- number of limitations (you cannot clone or fetch from
186
- it, nor push from nor into it), but is adequate if you
187
- are only interested in the recent history of a large project
188
- with a long history, and would want to send in fixes
189
- as patches.
185
+ number of limitations (you cannot clone or fetch from it, nor
186
+ push into it), but is adequate if you are only interested in
187
+ the recent history of a large project with a long history.
188
++
189
+Pushing from a shallow clone should be avoided if the git version on
190
+the receiver end is older than v1.7.10, or any other git
191
+implementation that does not perform connectivity check.
192
193
--[no-]single-branch::
194
Clone only the history leading to the tip of a single branch,