Re: [Issue 3304] New - svn-bisect

On Fri, Oct 31, 2008 at 12:21:44AM +0200, Daniel Shahaf wrote:
> Robert Millan wrote on Wed, 29 Oct 2008 at 20:38 +0100:
> > On Wed, Oct 29, 2008 at 07:59:10PM +0200, Daniel Shahaf wrote:
> > > Neels J Hofmeyr wrote on Mon, 27 Oct 2008 at 06:25 +0100:
> > > > Let's see what others have to say on the script itself.
> > >
> > > I don't see the part where it runs some external script to determine which
> > > way to continue the search.
> >
> > Hi!
> >
> > AFAIK, last known-good revision + first known-bad revision is enough
> > information to determine what to try next. At each interation (including
> > the first one), these are specified either by the user ("svn-bisect bad xxx")
> > or obtained from "svn info" output ("svn-bisect bad").
> >
>
> ... and the user is supposed to implement (himself) a loop that calls
> your script with the right argument?

Yes. This is intentional; it is inspired by git-bisect which operates
similarly:

  http://www.kernel.org/pub/software/scm/git/docs/git-bisect.html

I think this is highly desireable as many people are already used to this
procedure (and I think it's a reasonably good one anyway).

A typical user session would be:

  svn-bisect start
  svn-bisect bad 4321 # mark 4321 as bad
  svn-bisect good 1234 # mark 1234 as good
  # svn-bisect picks a new revision and updates to it
  # user tests it
  svn-bisect bad # user determined it is bad
  # svn-bisect picks a new revision and updates to it
  etc

-- 
Robert Millan
  The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
  how) you may access your data; but nobody's threatening your freedom: we
  still allow you to remove your data and not access it at all."
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org