From: Pranit Bauva <pranit.bauva@gmail.com>
To: git@vger.kernel.org
Cc: Pranit Bauva <pranit.bauva@gmail.com>,
Matthie.Moy@grenoble-inp.fr, christian.couder@gmail.com,
chriscool@tuxfamily.org, gitster@pobox.com
Subject: [RFC/PATCH 3/3] bisect--helper: `get_terms` & `bisect_terms` shell function in C
Date: Mon, 27 Jun 2016 02:14:11 +0530 [thread overview]
Message-ID: <20160626204411.19919-3-pranit.bauva@gmail.com> (raw)
In-Reply-To: <20160626204411.19919-1-pranit.bauva@gmail.com>
Reimplement the `get_terms` and `bisect_terms` shell function in C and
add `bisect-terms` subcommand to `git bisect--helper` to call it from
git-bisect.sh .
Using `--bisect-terms` subcommand is a temporary measure to port shell
function in C so as to use the existing test suite. As more functions
are ported, this subcommand will be retired and will be called by some
other methods.
Mentored-by: Christian Couder <chriscool@tuxfamily.org>
Signed-off-by: Pranit Bauva <pranit.bauva@gmail.com>
---
builtin/bisect--helper.c | 49 +++++++++++++++++++++++++++++++++++++++++++++++-
git-bisect.sh | 35 ++--------------------------------
2 files changed, 50 insertions(+), 34 deletions(-)
diff --git a/builtin/bisect--helper.c b/builtin/bisect--helper.c
index 9a289a1..51a408c 100644
--- a/builtin/bisect--helper.c
+++ b/builtin/bisect--helper.c
@@ -359,6 +359,41 @@ static int bisect_next_check(const struct bisect_terms *state, const char *term)
return 0;
}
+static int get_terms(struct bisect_terms *term)
+{
+ FILE *fp;
+ fp = fopen(git_path_bisect_write_terms(), "r");
+ if (!fp)
+ return -1;
+
+ bisect_terms_reinit(term);
+ if (strbuf_getline(&term->term_bad, fp) == EOF)
+ return -1;
+ if (strbuf_getline(&term->term_good, fp) == EOF)
+ return -1;
+ return 0;
+}
+
+static int bisect_terms(struct bisect_terms *term, const char *arg)
+{
+ if (get_terms(term)) {
+ fprintf(stderr, "no terms defined\n");
+ return -1;
+ }
+ if (!arg) {
+ printf("Your current terms are %s for the old state\nand "
+ "%s for the new state.\n", term->term_good.buf,
+ term->term_bad.buf);
+ return 0;
+ }
+ if (one_of(arg, "--term-good", "--term-old", NULL))
+ printf("%s\n", term->term_good.buf);
+ if (one_of(arg, "--term-bad", "--term-new", NULL))
+ printf("%s\n", term->term_bad.buf);
+
+ return 0;
+}
+
int cmd_bisect__helper(int argc, const char **argv, const char *prefix)
{
enum {
@@ -369,7 +404,8 @@ int cmd_bisect__helper(int argc, const char **argv, const char *prefix)
CHECK_EXPECTED_REVS,
BISECT_WRITE,
CHECK_AND_SET_TERMS,
- BISECT_NEXT_CHECK
+ BISECT_NEXT_CHECK,
+ BISECT_TERMS
} cmdmode = 0;
int no_checkout = 0, res = 0;
struct option options[] = {
@@ -389,6 +425,12 @@ int cmd_bisect__helper(int argc, const char **argv, const char *prefix)
N_("check and set terms in a bisection state"), CHECK_AND_SET_TERMS),
OPT_CMDMODE(0, "bisect-next-check", &cmdmode,
N_("check whether bad or good terms exist"), BISECT_NEXT_CHECK),
+ OPT_CMDMODE(0, "bisect-terms", &cmdmode,
+ N_("print out the bisect terms"), BISECT_TERMS),
+ OPT_ARGUMENT("term-bad", "handle this in an individual function"),
+ OPT_ARGUMENT("term-good", "handle this in an individual function"),
+ OPT_ARGUMENT("term-new", "handle this in an individual function"),
+ OPT_ARGUMENT("term-old", "handle this in an individual function"),
OPT_BOOL(0, "no-checkout", &no_checkout,
N_("update BISECT_HEAD instead of checking out the current commit")),
OPT_END()
@@ -450,6 +492,11 @@ int cmd_bisect__helper(int argc, const char **argv, const char *prefix)
}
res = bisect_next_check(&state, argv[2]);
break;
+ case BISECT_TERMS:
+ if (argc != 0 && argc != 1)
+ die(_("--bisect-terms requires 0 or 1 argument"));
+ res = bisect_terms(&state, argc ? argv[0] : NULL);
+ break;
default:
die("BUG: unknown subcommand '%d'", cmdmode);
}
diff --git a/git-bisect.sh b/git-bisect.sh
index 51b0a6b..5723601 100755
--- a/git-bisect.sh
+++ b/git-bisect.sh
@@ -355,7 +355,7 @@ bisect_replay () {
"$TERM_GOOD"|"$TERM_BAD"|skip)
git bisect--helper --bisect-write "$command" "$rev" "$TERM_GOOD" "$TERM_BAD" || exit;;
terms)
- bisect_terms $rev ;;
+ git bisect--helper --bisect-terms $rev ;;
*)
die "$(gettext "?? what are you talking about?")" ;;
esac
@@ -437,37 +437,6 @@ get_terms () {
fi
}
-bisect_terms () {
- get_terms
- if ! test -s "$GIT_DIR/BISECT_TERMS"
- then
- die "$(gettext "no terms defined")"
- fi
- case "$#" in
- 0)
- gettextln "Your current terms are $TERM_GOOD for the old state
-and $TERM_BAD for the new state."
- ;;
- 1)
- arg=$1
- case "$arg" in
- --term-good|--term-old)
- printf '%s\n' "$TERM_GOOD"
- ;;
- --term-bad|--term-new)
- printf '%s\n' "$TERM_BAD"
- ;;
- *)
- die "$(eval_gettext "invalid argument \$arg for 'git bisect terms'.
-Supported options are: --term-good|--term-old and --term-bad|--term-new.")"
- ;;
- esac
- ;;
- *)
- usage ;;
- esac
-}
-
case "$#" in
0)
usage ;;
@@ -498,7 +467,7 @@ case "$#" in
run)
bisect_run "$@" ;;
terms)
- bisect_terms "$@" ;;
+ git bisect--helper --bisect-terms "$@" ;;
*)
usage ;;
esac
--
2.9.0
prev parent reply other threads:[~2016-06-26 20:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-26 20:44 [RFC/PATCH 1/3] bisect--helper: `check_and_set_terms` shell function in C Pranit Bauva
2016-06-26 20:44 ` [RFC/PATCH 2/3] bisect--helper: `bisect_next_check` " Pranit Bauva
2016-06-26 20:44 ` Pranit Bauva [this message]
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=20160626204411.19919-3-pranit.bauva@gmail.com \
--to=pranit.bauva@gmail.com \
--cc=Matthie.Moy@grenoble-inp.fr \
--cc=chriscool@tuxfamily.org \
--cc=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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).