Re: can't 'svn cp' *twice* - bug or prohibited?

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

On Monday 09 December 2002 14:25, Alexis Huxley wrote:
> Doh! Thanks! :-) Still wondering *why* though ...

I guess because Subversion's philosophy is to never destroy data. Even though
file2 is unmodified locally, Subversion still wants you to explicitely "svn
remove" it before it will allow you to overwrite it.

This avoids any suprises if, for example, file2 had been committed by someone
else and you simply didn't notice that it existed. Even though the old
version would still be recoverable from the repository, it's better to
require explicit deletion.

- --
Peter Davis
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQE99S0thDAgUT1yirARAi+6AJ9jzYNRGBmA5o4sJL4GW2fLi5IPpgCfe3hU
OcypeGhtgI8SENpAOl7XHtA=
=JMSQ
-----END PGP SIGNATURE-----

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Dec 10 00:56:25 2002