Comment 1 for bug 1053778

I've been told that `bzr status --versioned` might be a workaround. In some use-cases it probably would achieve the desired results. A corollary issue is that --versioned does not seem as intuitive as --no-recurs, especially when someone is migrating over to bzr from something like <cough>cvs</cough>, where things can be done locally as opposed to recursively. bzr is attractive because it seems to try and largely succeed at letting people use various workflows that they are used to in other VCS. Adding --no-recurse would help in this regard.