[darcs-users] [patch106] resolve issue1208: trackdown --bisect (complete branch...

[Max Battcher]

Eric Kow wrote:
> 1. What problem does the proposed feature solve?
> 
>    EYK: Efficiently identifying a set of patches in the repository which
>    cause a test to pass (or was it fail?).  We currently have plain old
>    darcs trackdown, but it only works one patch a time, which makes it
>    rather painful.  Trackdown --bisect would presumably be a lot faster.
[snip]
>    Also, could we even take a step further and pro-actively enhance the
>    user interface by renaming darcs trackdown to darcs test.  The idea
>    then is that darcs test by itself just runs the test, and
>    darcs test --trackdown and darcs test --bisect do trackdown-ish tasks?

The obvious question here, particularly in the pro-active case: if 
--bisect is preferable in most/all cases (it should be faster in most 
cases, right?), perhaps --bisect should be the default "trackdown" and 
the current one renamed/deprecated?

That is, what are the use cases where one would prefer existing 
trackdown over trackdown --bisect?

--
--Max Battcher--
http://worldmaker.net