Hi, On Fri, Mar 09, 2012 at 02:05:37PM -0700, Michael Hendricks wrote: > I propose that 'trackdown --interactive' pause for each patch and ask > the user "Does this version work correctly? [yn]" If the user answers > 'y', it's treated the same as the test passing. If he answers 'n', > it's treated as a test failure. Darcs would also have to indicate the > temporary directory where the code resides, so the user knows where to
Indeed. > test. There would also be a 'q' command to stop the trackdown early. Or follow git bissect path (darcs returns, and trackdown --good, --bad and --quit continue or abort). Of course, it requires to save the current trackdown state, but it is more resilient to crashes, inadvertently quitting darcs, etc. > Does this sound useful to others? If so, I'll create an issue for it. > Would I be correct to assign this a ProbablyEasy tag? I believe so, because it does not require a deep understanding of darcs internals. But it would nevertheless be more work than any other ProbablyEasy bug I’ve solved in the past. Best regards, -- Gabriel _______________________________________________ darcs-users mailing list [email protected] http://lists.osuosl.org/mailman/listinfo/darcs-users
