<div class="gmail_quote">On Tue, May 5, 2009 at 10:48 PM, Robert Collins <<a href="mailto:robert.collins@canonical.com">robert.collins@canonical.com</a>> wrote: <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> So 'bzr check' currently takes parameters allowing control of checking repo/branch/tree. Are there actual use cases for this? I'd like to have check just check whatever is present [and do it quickly yada yada yada]. -Rob </blockquote></div> As a user of bzr in production environments, I will tell you that taking shortcuts in integrity tests of any kind is almost never a good choice. If checking my repo/branch/tree (s) takes hours, it's worth the peace of mind that comes from a cron job. It's fine if there are options to selectively disable tests, but the default should be to check everything that is checkable. This protects the naive and empowers the experts. -M