[MERGE][#74101] Make `bzr remove-tree` not remove trees with uncommitted changes by default

[Aaron Bentley]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

John Arbash Meinel wrote:
> So it *does* leave modified files available. And doing:
> 
> $ bzr co
> Conflict adding file bzr.  Moved existing file to bzr.moved.
> 
> So... not necessarily optimal. I'm not sure what the best route is. For
> example, what if you have 'unknown' files?

We get that behviour on checkout because we're specifically asking for
it.  Existing files with identical contents are not moved.  Only
modified files are moved.

It felt like the conservative choice, but if it's not what we want, we
can easily change it.

Aaron
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFI1WhX0F+nu1YWqI0RAgKYAJ92T/qAuG3bT1vbjRp9pke0aZ2PmwCcCAYx
gNwco4E+9N6kdZV+zClLoWw=
=ATdB
-----END PGP SIGNATURE-----