On Oct 30, 2008, at 21:13, paptimusx wrote:
> How should I do to return it to the state before Warkingcopy is
> changed?
>
> I thought seemed to have to commit it after phase 1...
>
> I done:
>
> 0)% svn rename TTTTT.DEP TTTTT.dep
> svn: Cannot move path 'TTTTT.dep' into itself
Yes, case-only renames are problematic on case-insensitive
filesystems, like the ones Windows and Mac OS X usually use. Here's
how you work around it:
http://subversion.tigris.org/faq.html#case-change
To fix your working copy now, the easiest might be to simply delete
it and check out a new one. That's assuming you have no other pending
changes in it.
> 1)% svn mv TTTTT.DEP xx
> 2)% svn mv xx TTTTT.dep
>
> 3)% svn ci
> svn: Working copy '**********************' locked
> svn: run 'svn cleanup' to remove locks (type 'svn help cleanup'
> for details)
>
> Oops!
>
> 4)% svn revert -R .
> svn: Working copy '.' locked
> svn: run 'svn cleanup' to remove locks (type 'svn help cleanup'
> for details)
>
> 5)% svn cleanup
> svn: In directory '.'
> svn: Error processing command 'committed' in '.'
> svn: Log command for directory 'TTTTT.DEP' is mislocated
>
>
>
> % ver
> Microsoft Windows XP [Version 5.1.2600]
> % svn --version -q
> 1.5.2
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-10-31 07:05:03 CET