Branko Čibej [mailto:br...@apache.org] wrote: > Because that's how 'svn copy' is supposed to work, and is also documented. > It works the same way as a recursive copy on a filesystem on Unix:
The destination ambiguity always was a bug magnet. It's a problem as old as cp. These days cp, or at least some versions of cp, has options --target-directory and --no-target-directory to resolve the ambiguity. I'm partial to the design where if the destination path ends in a slash then it's a container to copy into, and if it doesn't then it's a copy-and-rename. (Just sayin' - I know compatibility constraints make it almost impossible to change.) regards, Anders
