On 8-Aug-05, at 8:50 AM, Ben Collins-Sussman wrote:
> On Aug 8, 2005, at 7:00 AM, A.T.Hofkamp wrote:
>
>> + svn mv --force x y
>> svn: Cannot copy or move 'x': it's not in the repository yet; try
>> committing first
>>
>> Is this a known problem?
>
> Sure, because 'svn mv' is just 'svn cp; svn rm'. You cannot 'svn
> cp' a schedule-add file. Instead, 'svn revert' the schedule-add
> directory, 'mv' it with unix, then 'svn add' it again.
Are there any plans to make the svn command line smart enough to do
this on its own? Or is there a much grander plan involving the
implementation of true renames?
Scott
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Aug 8 15:41:11 2005