From: Christian Couder <chriscool@tuxfamily.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, Jeff King <peff@peff.net>
Subject: [PATCH v2 01/10] replace: refactor command-mode determination
Date: Sat, 17 May 2014 08:41:23 +0200 [thread overview]
Message-ID: <20140517064133.18932.23762.chriscool@tuxfamily.org> (raw)
In-Reply-To: <20140517062418.18932.21200.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.rc0.17.g651113e
next prev parent reply other threads:[~2014-05-17 6:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-17 6:41 [PATCH v2 00/10] replace: add option to edit a Git object Christian Couder
2014-05-17 6:41 ` Christian Couder [this message]
2014-05-17 6:41 ` [PATCH v2 02/10] replace: use OPT_CMDMODE to handle modes Christian Couder
2014-05-17 6:41 ` [PATCH v2 03/10] replace: factor object resolution out of replace_object Christian Couder
2014-05-17 6:41 ` [PATCH v2 04/10] replace: add --edit option Christian Couder
2014-05-17 6:41 ` [PATCH v2 05/10] replace: make sure --edit results in a different object Christian Couder
2014-05-17 7:03 ` Jeff King
2014-05-17 6:41 ` [PATCH v2 06/10] replace: refactor checking ref validity Christian Couder
2014-05-17 6:41 ` [PATCH v2 07/10] replace: die early if replace ref already exists Christian Couder
2014-05-17 7:05 ` Jeff King
2014-05-17 6:41 ` [PATCH v2 08/10] replace: add tests for --edit Christian Couder
2014-05-17 7:14 ` Jeff King
2014-05-17 6:41 ` [PATCH v2 09/10] replace: add --edit to usage string Christian Couder
2014-05-17 6:41 ` [PATCH v2 10/10] Documentation: replace: describe new --edit option Christian Couder
2014-05-17 7:23 ` Jeff King
2014-05-17 7:24 ` [PATCH v2 00/10] replace: add option to edit a Git object Jeff King
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140517064133.18932.23762.chriscool@tuxfamily.org \
--to=chriscool@tuxfamily.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).