git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Ealdwulf Wuffinga <ealdwulf@googlemail.com>
Cc: Clemens Buchacher <drizzd@aon.at>,
	Christian Couder <chriscool@tuxfamily.org>,
	Sam Vilain <sam@vilain.net>,
	Git Mailing List <git@vger.kernel.org>
Subject: Re: RFE: "git bisect reverse"
Date: Thu, 28 May 2009 14:54:02 -0700	[thread overview]
Message-ID: <4A1F07FA.6040008@zytor.com> (raw)
In-Reply-To: <efe2b6d70905281407x56bb788aq3dba4b27eb91d7a6@mail.gmail.com>

Ealdwulf Wuffinga wrote:
> 
> It would fit a lot better into this algorithm to have some model of
> the probability that a commit will cause a skip. It doesn't actually
> have to be a very good one, because if it's poor it will only make the
> search slightly less efficient, not affect the reliability of the
> final result.
> 

How about simply modelling it linearly, with 100% probability for known
skip point, 0% for a known good/bad point, and a linear gradient in
between?  It's probably a good enough model.  In practice, it will
vastly overestimate the probability of a skip, so if a linear model
turns out to be too conservative, I would probably just try to model it
as a higher-order power function.

	-hpa

  reply	other threads:[~2009-05-28 21:54 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
2009-05-28  3:11             ` H. Peter Anvin
2009-05-28 21:07               ` Ealdwulf Wuffinga
2009-05-28 21:54                 ` H. Peter Anvin [this message]
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=4A1F07FA.6040008@zytor.com \
    --to=hpa@zytor.com \
    --cc=chriscool@tuxfamily.org \
    --cc=drizzd@aon.at \
    --cc=ealdwulf@googlemail.com \
    --cc=git@vger.kernel.org \
    --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).