Comment 7 for bug 215612

There is one more use case:

Suppose I lose the connection in the middle of an upload. Then, I won't be able to do bzr-upload again, because some files were already deleted, and I'm be forced to do a full upload (which is longer, so it's even more likely to fail due to connection problems). I think bzr-upload should be robust in this respect, especially since it's targetting low-end hosting services.

My own use case is a bit different: I added symlinks to my branch, and bzr-upload blew on them (Bug #214825). A silly mistake like that shouldn't force me to upload the whole tree again.