Revert "git-clone.txt: remove the restriction on pushing from a shallow clone"
This reverts commit dacd2bcc414e0b7aac36aaa400da0a743c4741cc. "It fails reliably without corrupting the receiving repository when it should fail" may be better than the situation before the receiving end was hardened recently, but the fact that sometimes the push does not go through still remains. It is better to advice the users that they cannot push from a shallow repository as a limitation before they decide to use (or not to use) a shallow clone. Signed-off-by: Junio C Hamano <gitster@pobox.com>
Junio C Hamano committed
Jul 15, 2013 at 08:31 UTC
5333f2afc4f5c6365845b25ffc22a91379b84c58
1 file changed
+5
-7
Documentation/git-clone.txt
+5
-7
@@ -182,13 +182,11 @@ 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 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.
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.
190
191
--[no-]single-branch::
192
Clone only the history leading to the tip of a single branch,