From: Junio C Hamano <gitster@pobox.com>
To: Christian Couder <chriscool@tuxfamily.org>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 4/5] bisect--helper: add "--next-exit" to output bisect results
Date: Mon, 20 Apr 2009 01:44:34 -0700 [thread overview]
Message-ID: <7vprf7k93h.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <20090419115607.c7089503.chriscool@tuxfamily.org> (Christian Couder's message of "Sun, 19 Apr 2009 11:56:07 +0200")
Christian Couder <chriscool@tuxfamily.org> writes:
> The goal of this patch is to port more shell code from the "bisect_next"
> function in "git-bisect.sh" to C code in "builtin-bisect--helper.c".
>
> So we port the code that interprets the bisection result and stops or
> continues (by checking out the next revision) the bisection process.
>
> Signed-off-by: Christian Couder <chriscool@tuxfamily.org>
Just to make sure I understand correctly, with this and patch 5/5, we can
then drop the --next-vars helper command, right?
> @@ -16,6 +17,12 @@ static const char **rev_argv;
> static int rev_argv_nr;
> static int rev_argv_alloc;
>
> +static const unsigned char *current_bad_sha1;
> +
> +static const char *argv_diff_tree[] = {"diff-tree", "--pretty", NULL, NULL};
> +static const char *argv_checkout[] = {"checkout", "-q", NULL, "--", NULL};
> +static const char *argv_show_branch[] = {"show-branch", NULL, NULL};
I do appreciate that you kept this step in "rewrite in C" theme a straight
rewrite to still call out the executables. We can turn these into
internal calls in future steps, but that is a separate issue.
I suspect that the show-branch call outlived its usefulness with this
patch; it will now be a low hanging fruit to call format_commit_message()
internally to reduce one fork+exec.
Thanks, queued.
next prev parent reply other threads:[~2009-04-20 8:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-19 9:56 [PATCH 4/5] bisect--helper: add "--next-exit" to output bisect results Christian Couder
2009-04-20 7:25 ` Stephen Boyd
2009-04-21 5:51 ` Christian Couder
2009-04-20 8:44 ` Junio C Hamano [this message]
2009-04-21 5:57 ` Christian Couder
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=7vprf7k93h.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=chriscool@tuxfamily.org \
--cc=git@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.