On Feb 10, 2005, at 11:28 PM, Ben Collins-Sussman wrote:
> And honestly, it's not svn's job to send announcements about things
> being renamed.
Ah, but it is, sort of. If you used 'svn move' and commit the change,
when others do a 'svn update' the change should be reflected in the
working copy, and the update should display a message to indicate what
was done (or what it couldn't do), right? If there is an error
message, as you stated, it needs to be clear.
The message "unable to replace a directory from within" *is* cryptic in
the context of running an update, because the user that invoked 'svn
update' isn't trying to move any directories.
The conversation "hey, didn't you read the announcement? The branch
moved to 'barbranch'. Just run 'svn switch' to the new URL." should be
entirely unnecessary, since Subversion should know exactly that is what
happened it could report that itself. I believe the root of the issue
is that Subversion doesn't fully understand "moves", using the current
"copy and delete" implementation, so I would figure that this error
message could be improved when proper move support is added.
Scott
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Feb 11 15:33:21 2005