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

Re: [PATCH] clone: detect extra arguments

From
Jeff King <peff@peff.net>
Date
Oct 30, 2009, 14:51 UTC
Message-ID
<20091030145108.GA881@coredump.intra.peff.net>
In-Reply-To
<20091030144525.GA22583@coredump.intra.peff.net>
On Fri, Oct 30, 2009 at 10:45:25AM -0400, Jeff King wrote:
> But looking at the usage message, there is some potential for cleanup.

Also, we should probably do this (I did it as a patch on master, though, as it is an independent fix):

-- >8 --
Subject: [PATCH] clone: fix --recursive usage message
Looks like a mistaken cut-and-paste in e7fed18a.
Signed-off-by: Jeff King <peff@peff.net>
---
 builtin-clone.c |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/builtin-clone.c b/builtin-clone.c
index 5762a6f..436e8da 100644
--- a/builtin-clone.c
+++ b/builtin-clone.c
@@ -61,7 +61,7 @@ static struct option builtin_clone_options[] = {
 	OPT_BOOLEAN('s', "shared", &option_shared,
 		    "setup as shared repository"),
 	OPT_BOOLEAN(0, "recursive", &option_recursive,
-		    "setup as shared repository"),
+		    "initialize submodules in the clone"),
 	OPT_STRING(0, "template", &option_template, "path",
 		   "path the template repository"),
 	OPT_STRING(0, "reference", &option_reference, "repo",
-- 
1.6.5.1.143.g1dab74.dirty
Previous: Jeff KingNext: Johan Herland
Message 5 of 6 in “clone: detect extra arguments”
  1. clone: detect extra argumentsJonathan Nieder, Oct 29, 2009
  2. Jeff KingOct 29, 2009
  3. Jonathan NiederOct 30, 2009
  4. Jeff KingOct 30, 2009
  5. Jeff KingOct 30, 2009
  6. Johan HerlandOct 31, 2009

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.