git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[PATCH] Revert "git-clone.txt: remove the restriction on pushing from a shallow clone"

From
Junio C Hamano <gitster@pobox.com>
Date
Jul 15, 2013, 15:35 UTC
Message-ID
<7vk3krdeeh.fsf_-_@alter.siamese.dyndns.org>
In-Reply-To
<CACsJy8DELmhBwBCk9hmg4EpQxGeCRDPaSEr5rYp=CiMjq8j54Q@mail.gmail.com>
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. ---

 * Unfortunately I thought the documentation update was a
   no-brainer and already applied it, so here is a revert.
 Documentation/git-clone.txt | 12 +++++-------
 1 file changed, 5 insertions(+), 7 deletions(-)
diff --git a/Documentation/git-clone.txt b/Documentation/git-clone.txt
index 85769b8..450f158 100644
--- a/Documentation/git-clone.txt
+++ b/Documentation/git-clone.txt
@@ -182,13 +182,11 @@ objects from the source repository into a pack in the cloned repository.
 --depth <depth>::
 	Create a 'shallow' 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.
-+
-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.
+	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.
 
 --[no-]single-branch::
 	Clone only the history leading to the tip of a single branch,
-- 
1.8.3.2-941-gda9c3c8
Previous: Junio C Hamano
Message 11 of 11 in “git-clone.txt: remove the restriction on pushing from a shallow clone”
  1. git-clone.txt: remove the restriction on pushing from a shallow cloneNguyễn Thái Ngọc Duy, Jul 12, 2013
  2. Junio C HamanoJul 12, 2013
  3. Junio C HamanoJul 12, 2013
  4. Duy NguyenJul 12, 2013
  5. Jonathan NiederJul 13, 2013
  6. Duy NguyenJul 14, 2013
  7. Junio C HamanoJul 14, 2013
  8. Duy NguyenJul 15, 2013
  9. Duy NguyenJul 15, 2013
  10. Junio C HamanoJul 15, 2013
  11. Revert "git-clone.txt: remove the restriction on pushing from a shallow clone"Junio C Hamano, Jul 15, 2013

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.