Comment 2 for bug 195134

On Sun, 2008-02-24 at 21:22 +0000, Robert Collins wrote:
> given that the loom itself provides a meta-status, you can revert the
> entire loom to undo all the merges done to threads since the last
> 'record', I don't think that the bzr philosophy is violated; we're just
> moving up a level. However, I think we should at minimum provide a hook
> to test each thread as the merge progesses.
>
> For instance, one could have in branch.conf
> thread_test = 'make check'
>
> then 'bzr switch upstream && bzr pull && bzr up-thread -a -m "Merging
> upstream."' will run 'make check' as it goes up each thread, stopping at
> the first error but otherwise committing with 'Merging upstream.'

I think the check at each level would be heavyweight for
some cases, for instance ./bzr selftest at each thread
would just take too long, so I would prefer to do it at
the top and then "bisect" if there was an error, however
I can see the reasoning.

Mentioning that, is there a use case for loom-bisect or similar?
I'll file another bug if you agree.

Thanks,

James