From: Ealdwulf Wuffinga <ealdwulf@googlemail.com>
To: Sam Vilain <sam@vilain.net>
Cc: Clemens Buchacher <drizzd@aon.at>,
Christian Couder <chriscool@tuxfamily.org>,
"H. Peter Anvin" <hpa@zytor.com>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: RFE: "git bisect reverse"
Date: Sun, 31 May 2009 23:41:47 +0100 [thread overview]
Message-ID: <efe2b6d70905311541y2576ef0enc66d619672d4ef34@mail.gmail.com> (raw)
In-Reply-To: <4A1F628F.9010407@vilain.net>
On Fri, May 29, 2009 at 5:20 AM, Sam Vilain <sam@vilain.net> wrote:
>
> I mean, can you port your algorithm from python to the git-bisect C
> source and therefore make something of benefit to existing 'git bisect'
> users ?
I haven't really looked at the git bisect code yet, but the algorithms
are so different that it would likely make the most sense to just add
my algorithm in parallel, rather than trying to combine them.
(Although my algorithm can handle the deterministic case as well,
you'd want to keep the original one too, because mine starts to get a
bit sluggish deciding which commit to test for larger commit ranges. )
It could still be driven by git-bisect script, though.
Converting it to C wouldn't be a trivial task, though, so I may not
get around to it. I'll probably write a more git-like frontend, and
maybe submit a patch to add it to the contrib directory, to get a
better idea of whether
there are actually any users for this feature, before deciding whether
to do the conversion.
Ealdwulf
next prev parent reply other threads:[~2009-05-31 22:42 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-26 22:21 RFE: "git bisect reverse" H. Peter Anvin
2009-05-27 3:00 ` Sam Vilain
2009-05-27 4:20 ` H. Peter Anvin
2009-05-27 5:26 ` Christian Couder
2009-05-27 21:11 ` Ealdwulf Wuffinga
2009-05-27 21:18 ` Clemens Buchacher
2009-05-27 22:07 ` Ealdwulf Wuffinga
2009-05-27 23:08 ` Sam Vilain
2009-05-28 20:29 ` Ealdwulf Wuffinga
2009-05-29 4:20 ` Sam Vilain
2009-05-31 22:41 ` Ealdwulf Wuffinga [this message]
2009-05-28 3:11 ` H. Peter Anvin
2009-05-28 21:07 ` Ealdwulf Wuffinga
2009-05-28 21:54 ` H. Peter Anvin
2009-05-31 22:18 ` Ealdwulf Wuffinga
2009-05-27 20:11 ` Christian Couder
2009-05-27 8:22 ` Nanako Shiraishi
2009-05-27 20:26 ` Matthieu Moy
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=efe2b6d70905311541y2576ef0enc66d619672d4ef34@mail.gmail.com \
--to=ealdwulf@googlemail.com \
--cc=chriscool@tuxfamily.org \
--cc=drizzd@aon.at \
--cc=git@vger.kernel.org \
--cc=hpa@zytor.com \
--cc=sam@vilain.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).