"Erik Anderson" <erikba@teamworkgroup.com> writes:
> Due to some stale state information or something, TortoiseSVN issued
> an "svn add" command for a file that was already in the working
> directory as a different capitalization. Instead of the windows
> subversion libraries rejecting the add request, it happily added the
> file to the working directory, and both the old and the new
> capitalization were successfully sent on the next commit.
>
> My question I guess is this: even under a completely messed up
> TortoiseSVN making calls to the subversion libraries, should the
> subversion on a windows client be willing to add a file to a working
> directory that was already a member through a different
> capitalization? And is there a currently a check for this in
> subversion 1.0, or is this a new feature request?
I'm very surprised that it was able to do this at all, actually.
If you want to undo the change, and can't undo it in the local working
copy, a good way is to do it via URLs, for example
C:\>svn rm -F logmsg.txt http://URL/TO/THE/NEW/FILE
or
C:\>svn mv -F logmsg.txt http://URL/TO/NEW/FILE http://URL/TO/NEW/FILE2
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Aug 10 00:49:12 2004