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

[PATCH v1 1/4] replace: refactor command-mode determination

From
Christian Couder <chriscool@tuxfamily.org>
Date
Apr 26, 2014, 20:00 UTC
Message-ID
<20140426200058.21546.78905.chriscool@tuxfamily.org>
In-Reply-To
<20140426194404.21546.82305.chriscool@tuxfamily.org>
From: Jeff King <peff@peff.net>

The git-replace command has three modes: listing, deleting, and replacing. The first two are selected explicitly. If none is selected, we fallback to listing when there are no arguments, and replacing otherwise.

Let's figure out up front which operation we are going to do, before getting into the application logic. That lets us simplify our option checks (e.g., we currently have to check whether a useless "--force" is given both along with an explicit list, as well as with an implicit one).

This saves some lines, makes the logic easier to follow, and will facilitate further cleanups.

Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Christian Couder <chriscool@tuxfamily.org>
---
 builtin/replace.c | 14 ++++++--------
 1 file changed, 6 insertions(+), 8 deletions(-)
diff --git a/builtin/replace.c b/builtin/replace.c
index b62420a..28db96f 100644
--- a/builtin/replace.c
+++ b/builtin/replace.c
@@ -182,12 +182,16 @@ int cmd_replace(int argc, const char **argv, const char *prefix)
 
 	argc = parse_options(argc, argv, prefix, options, git_replace_usage, 0);
 
+	if (!list && !delete)
+		if (!argc)
+			list = 1;
+
 	if (list && delete)
 		usage_msg_opt("-l and -d cannot be used together",
 			      git_replace_usage, options);
 
-	if (format && delete)
-		usage_msg_opt("--format and -d cannot be used together",
+	if (format && !list)
+		usage_msg_opt("--format cannot be used when not listing",
 			      git_replace_usage, options);
 
 	if (force && (list || delete))
@@ -207,9 +211,6 @@ int cmd_replace(int argc, const char **argv, const char *prefix)
 		if (argc != 2)
 			usage_msg_opt("bad number of arguments",
 				      git_replace_usage, options);
-		if (format)
-			usage_msg_opt("--format cannot be used when not listing",
-				      git_replace_usage, options);
 		return replace_object(argv[0], argv[1], force);
 	}
 
@@ -217,9 +218,6 @@ int cmd_replace(int argc, const char **argv, const char *prefix)
 	if (argc > 1)
 		usage_msg_opt("only one pattern can be given with -l",
 			      git_replace_usage, options);
-	if (force)
-		usage_msg_opt("-f needs some arguments",
-			      git_replace_usage, options);
 
 	return list_replace_refs(argv[0], format);
 }
-- 
1.9.1.636.g20d5f34
Previous: Christian CouderNext: Christian Couder
Message 2 of 7 in “replace: add option to edit a Git object”
  1. 0/4 replace: add option to edit a Git objectChristian Couder, Apr 26, 2014
  2. 1/4 replace: refactor command-mode determinationChristian Couder, Apr 26, 2014
  3. 2/4 replace: use OPT_CMDMODE to handle modesChristian Couder, Apr 26, 2014
  4. 3/4 replace: factor object resolution out of replace_objectChristian Couder, Apr 26, 2014
  5. 4/4 replace: add --edit optionChristian Couder, Apr 26, 2014
  6. Jeff KingApr 29, 2014
  7. Junio C HamanoApr 29, 2014

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.