Re: Preventing accidental duplicate branching on 1.4.2

Greetings, Eric Olson!

> We're still using the svn 1.4 branch and I've noticed something that
> doesn't seem right to me. As I understand it, the correct way to create
> a branch is: svn copy [...]/trunk/ [...]/branches/foo/ -m "Creating foo
> branch"

> Which works exactly as I expected. If I turn around and immediately run
> the same command, which I was expecting to fail because the foo branch
> already exists, svn instead creates /branches/foo/trunk/. A third
> execution of that same command throws an error because the directory
> already exists.

> Is that the expected behavior? I'm just worried about svn users
> branching twice or accidentally reusing an old branch name.

Well, right command is

svn copy [...]/trunk [...]/branches/foo

(notice the difference)
What you see is a side-effect of proper handling of given command (in
filesystem terms)
Means, it's unexpected, but intended way of things.

--
WBR,
 Andrey Repin (anrdaemon_at_freemail.ru) 05.05.2009, <19:02>
Sorry for my terrible english...
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2070183
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].