[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: [Issue 3304] New - svn-bisect

From: Robert Millan <rmh_at_aybabtu.com>
Date: Wed, 29 Oct 2008 20:38:03 +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:
> >
> > Dude, I guess it would have been better to post a mail to
> > dev_at_subversion.tigris.org instead of opening an issue marked "DEFECT" to
> > contribute a script you wrote. You must have ignored quite a bunch of large
> > bold print in red frames on your way to the issue creator... ?
> >
> > 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.


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").

This CLI is inspired by the one in git. All in all, it seems to be designed
so that the implementation can be made without much complexity.

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
Received on 2008-10-30 01:34:32 CET

This is an archived mail posted to the Subversion Dev mailing list.