svn bisect

Hi All,

I am currently trying to implement "svn bisect" subcommand. Yes, I know
there are some good scripts out there that work, but it's not part of
our API. I figured this would be a decent addition to our code. Here are
a few things I wanted to ask the community:

1. Would it be better if the command ran as a single process throughout
the bisect operation and keep track of things in memory, or should it
work like the scripts that are out there which keep track of things on
disk (in a persistent file)?

2. For the scripts that are currently out there, the 'probe script' runs
in the environment in which the bisect script was run. Is it safe to
have a subcommand that runs an external script? Is there a precedent to
this kind of behaviour?

3. Will this feature be considered at all (if it is any good) or am I
simply doing something to exercise my brain cells?

Regards,
Arwin Arni
Received on 2011-06-21 09:45:48 CEST