| commit | dacd2bcc414e0b7aac36aaa400da0a743c4741cc | |
| author | Nguyễn Thái Ngọc Duy <pclouds@gmail.com> | |
| Fri, 12 Jul 2013 05:37:42 +0000 (12 12:37 +0700) | ||
| committer | Junio C Hamano <gitster@pobox.com> | |
| Fri, 12 Jul 2013 19:03:28 +0000 (12 12:03 -0700) | ||
| tree | be683bfad7770055ba6f65c64ffd39ae079ced3c | treesnapshot (tar.gz zip) |
| parent | 911011aacc78dfa8ac81a5e631cb86bb69fd66e1 | commitdiff |
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>
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>
| Documentation/git-clone.txt | diffblobblamehistory |