Re: Accurate problem description

> I'd like to put in a vote AGAINST subversion renaming my directories. If I
> want em renamed, I'll do it myself.
>
> I make sure things that shouldn't be in my build directories aren't, and
> this problem isn't svn's, it belongs to whoever deleted a directory and made
> a new one with the same name (and then assumed everything would be fine).

I understand your point of view.
You have good luck that you don't have this problem.

The problem is: As explained in previous posts,
this approach is simply not possible many situations
(including our case).

And I simply don't know any method how to solve this problem,
except the ugly hacks described in my previous post.

Besides that you are against something,
what solution do you suggest?

Maybe svn update could get a new parameter like
"--move-way" (not an ideal name)?
Then a normal svn update could say:
"Cannot replace directory qqq because it contains unversioned
files. You may use the option --move-away to move the old
directory out of the way."
Such a message would give the user a hint how to solve
the problem.

Cheers,
Folker

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Dec 19 23:33:03 2003