> Fuhrmann<stefanfuhrmann_at_alice-dsl.de> wrote:
> > Stefan Küng <tortoisesvn_at_gmail.com> wrote:
> >> > * Explorer context menu and / or log
> >> > - "Bisect" to automatically and semi-
> >> > automatically find offending revisions
> >> What do you mean by "offending revisions"? What would such a feature
> >> actually do?
> > GIT introduced this feature. The basic idea
> > is to specify a "good" (working) revision
> > and a "bad" (broken) revision plus some script.
> > Using bisection (based on length of actual
> > history not rev number arithmetics), the
> > first "bad" revision can be found.
> > The script is used to decide upon "good" or
> > "bad". For TSVN, I would like to support
> > fully automatic operation (user specifies
> > test and optional cleanup scripts etc.)
> > as well as guided operation where the user
> > has to press either to 'good' or 'bad' button.
> Why not implement this in Subversion directly, so that you can use it
> in TSVN and someone else can implement it as 'svn bisect' ? Seems like
> a useful feature to me.
The actual "functionality" is fairly simple. What is less
obvious is options, UI and interaction (similar to the
interactive conflict resolution that was added only years
after the original merge interface).
Therefore, I would take an approach similar to what was
done with the 'blame' feature: Have one working client
implementation as a prototype and move the core functionality
to the SVN core libs afterwards. The TSVN adaptions for
the second step are certainly small.
To unsubscribe from this discussion, e-mail: [dev-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2009-08-17 21:52:36 CEST