This was the point I was trying to make. SVN should not fail on copy
because the dir is there, rather it should put possible contents in
it, just like cp does. Just failing completely is wrong I think
since the copy is perfectly valid.
Thanks
R
On Apr 13, 2005, at 2:57 AM, Saulius Grazulis wrote:
> Admitedly, on the third copy 'cp' behaves differently from svn:
>
> saulius@kolibris: copies/ > cp -a myProject/trunk/Dir3/SubDir1
> myProject/tags/tag1
>
> saulius@kolibris: copies/ > ls -l myProject/tags/tag1
> total 4
> drwxr-xr-x 2 saulius 4096 Apr 13 09:51 SubDir1/
> -rw-r--r-- 1 saulius 0 Apr 13 09:50 file1.txt
>
> saulius@kolibris: copies/ > ls -l myProject/tags/tag1/SubDir1/
> total 0
> -rw-r--r-- 1 saulius 0 Apr 13 09:50 file2.txt
> -rw-r--r-- 1 saulius 0 Apr 13 09:51 file3.txt
>
> Thus, there was no error message, and file 'file3.txt' ended up in
> myProject/tags/tag1/SubDir1/. Well, I would say this is a bug in
> 'cp', not in
> Subversion ;)...
Robert S. Sfeir
yosemitesam(at)gmailNOSPAM.com
Received on Wed Apr 13 14:32:37 2005