Thread (7 messages) flat view 7 messages, 5 authors, 2016-06-15

Re: Does cloning a shallow repo require special setting in the cloned one?

From: Jeff King <hidden>
Date: 2016-06-15 22:46:17

Possibly related (same subject, not in this thread)

On Thu, Feb 26, 2009 at 12:17:36PM +0100, Johannes Schindelin wrote:
quoted hunk ↗ jump to hunk
I think it is way better to warn, since "--depth" is usually passed out of 
concerns about disk space.  And --shared should shut that concern up 
rather nicely.
diff --git a/builtin-clone.c b/builtin-clone.c
index c338910..5831034 100644
--- a/builtin-clone.c
+++ b/builtin-clone.c
@@ -511,8 +511,11 @@ int cmd_clone(int argc, const char **argv, const char *prefix)
 	refspec.src = src_ref_prefix;
 	refspec.dst = branch_top.buf;
 
-	if (path && !is_bundle)
+	if (path && !is_bundle) {
+		if (option_depth)
+			warning("Ignoring --depth for local clone");
 		refs = clone_local(path, git_dir);
+	}
 	else {
 		struct remote *remote = remote_get(argv[0]);
 		transport = transport_get(remote, remote->url[0]);
That seems reasonable to me.

-Peff
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help