Ben Collins-Sussman wrote:
>
> On Jun 30, 2005, at 2:14 PM, Clint Chapman wrote:
>
>>>
>> Is there a better way to fix the problem than (what I did) checking
>> out another working copy, copying all the changes over manually and
>> committing from the new working copy?
>
>
>
> I'm a little confused; when you checked out a fresh working copy,
> did you not see that the changes were already present, i.e. already
> existed in the repository?
>
>
Yes, the rename was committed ok (when I checked it out the renamed
directory change was there). The problem was that I had also made
changes to some files in the renamed directory and when I went to commit
those changes it complained that certain directories inside the renamed
directory's working copy didn't exist in the repository (apparently the
working copy still looked as if the rename hadn't happened while it had
happened in the repository). The only way I could figure out to fix it
was checking out another working copy, copying all the changes over
manually and committing from the new working copy. An update and clean
up didn't fix anything. I was wondering if there was a better way to
get those files (in my semi-successfully renamed directory) committed.
--
Clint Chapman
Luminos Industries Ltd.
Phone: 613-225-7661
www.luminosindustries.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Jun 30 22:21:55 2005