From: Christian Couder <chriscool@tuxfamily.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: [PATCH 0/5] port more "git bisect next" code to C
Date: Sun, 19 Apr 2009 11:55:34 +0200 [thread overview]
Message-ID: <20090419115534.f0473356.chriscool@tuxfamily.org> (raw)
This patch series moves code from the "bisect_next" shell function
in "git-bisect.sh" to C code in "builtin-bisect--helper.c".
To do that a "--next-exit" option to "git bisect--helper" is
added, and is used instead of the "--next-vars" option in
"bisect_next".
rev-list: make "estimate_bisect_steps" non static
rev-list: refactor printing bisect vars
bisect: move common bisect functionality in "bisect_common"
bisect--helper: add "--next-exit" to output bisect results
bisect: use "git bisect--helper --next-exit" in "git-bisect.sh"
bisect.c | 127 +++++++++++++++++++++++++++++++++++++++++++---
bisect.h | 7 +++
builtin-bisect--helper.c | 12 +++-
builtin-rev-list.c | 63 ++++++++++++-----------
git-bisect.sh | 39 +++-----------
5 files changed, 178 insertions(+), 70 deletions(-)
reply other threads:[~2009-04-19 9:58 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20090419115534.f0473356.chriscool@tuxfamily.org \
--to=chriscool@tuxfamily.org \
--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).