[MERGE][#74101] Make `bzr remove-tree` not remove trees with uncommitted changes by default
John Arbash Meinel
john at arbash-meinel.com
Sun Aug 31 15:18:16 BST 2008
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Lukáš Lalinský wrote:
> With this patch, ``bzr remove-tree`` will refuse to remove a tree with
> uncommitted changes, unless the ``--force`` option is specified.
>
> Lukas
>
>
I thought it would leave uncommitted files around, or at least was somehow
"safe". That may not be good enough but doing:
$ bzr branch bzr.dev test
$ cd test
$ echo "foo" >> bzr
$ bzr remove-tree .
$ ls
bzr
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?
John
=:->
PS> (Probably I like this change, but I at least want to discuss it before
reviewing.)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFIuqgoJdeBCYSNAAMRAsZ+AJ9AKpye/nGLtxI2Ec4u3yUyB1He2QCeKvCS
BRrOulxiAdCTvC8cD6JhkD0=
=VO4D
-----END PGP SIGNATURE-----
More information about the bazaar
mailing list