RFC: check UI

[Vincent Ladeuil]

>>>>> "robert" == Robert Collins <robert.collins at canonical.com> writes:

    robert> So 'bzr check' currently takes parameters allowing
    robert> control of checking repo/branch/tree. Are there
    robert> actual use cases for this?

    robert> I'd like to have check just check whatever is present
    robert> [and do it quickly yada yada yada].

I think check should, by default, check anything it can but
provides options to restrict the checks when you want. For
example if I'm tracking a tree or branch related problem, I don't
want to lose time checking the repo.

I'm not sure DWIM is worth the effort here...

A related point: I've been bitten in the past because I forgotten
to specify '-v' for a repo check that took day(s). So I'd like
check to *always* output data that may be needed to fix whatever
is found to be wrong (putting that info in .bzr.log is ok).

    Vincent