[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: svn copy onto itself is possible

From: C. Michael Pilato <cmpilato_at_collab.net>
Date: 2003-10-01 15:38:43 CEST

Lübbe Onken <L.Onken@rac.de> writes:

> 2) Second Copy
> svn copy http://myserver/myrepos/trunk/ http://myserver/myrepos/tags/Tag_01
> creates http://myserver/myrepos/Tag_01/trunk, when
> http://myserver/myrepos/Tag_01 already exists.
> This is where I'd expect a warning, that the destination already exist,
> telling you where the copy would really end up and allowing you to cancel or
> continue the operation.
> Maybe I wanted to create Tag_02 and just mistyped it?!? Maybe a
> day/week/month later I'll wonder where the tag I created a while ago has
> disappeared?

This behavior was chosen because it mimics the behavior of 'cp' on
Unix systems. 'cp' will not warn you when your target is an existing
directory -- it will simply copy your source as a sub-item of the
existing directory (with the same name).

Personally, I don't like this behavior. I am frequently bitten by it
when using 'mv' and 'cp' on Unix systems, so I know how frustrating
that can be. And I thought that at least the commit message editor
pop-up in Subversion would report the addition of the right path --
but it doesn't. At the very least, *that* is a bug.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Oct 1 15:40:03 2003

This is an archived mail posted to the Subversion Users mailing list.