Thanks to both of you for your perspective. I appreciate all of the point you make. My perspective is necessarily different from that of a bzr poweruser. I am obliged to worry about how less advanced users will hurt themselves. I need to weigh the benefits of a feature in the right hands against he risks of the same feature in the wrong hands. Sadly it it not always obvious until I have to get involved to help. For the most part, I think bzr does the right things by default. And I think plugins and gui front-ends are probably the right place for safety features. -M <div class="gmail_quote">On Tue, Apr 14, 2009 at 9:00 PM, Robert Collins <<a href="mailto:robert.collins@canonical.com" target="_blank">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;"> People also version their homedir from time to time... it would be annoying at the minimum for them to have to supply an option everytime - it would be an unbreakme option. 'bzr init new-dir' won't cause grief in the same way that 'bzr init' in a dir that is versioned can. In fact, I think the only time that 'bzr init [foo]' is arguably an error is when foo is *versioned* by a containing branch. That should be an error and should say 'use bzr split'. -Rob </blockquote></div>