Re: [Subclipse-users] Remove followed by add of same file

Mark Phippard wrote:

>> today I removed a file, and afterwards copied a different file to the
>> same old name. That resulted in a "remove" pending operation that didn't
>
>> go away once the file was recreated again.
>>
>> Is that on purpose somehow? Would it be possible that the pending remove
>
>> operation will silently be taken back or something like that?
>
> The delete is still pending and has to be committed. We have no way to
> know what you want to do here. It sounds like you wanted to do a Revert
> and then copy in the new file so that it looked like a modification.

I ran into the same bug today but during a refactoring. It left my
project in a sad state (all the imports were already changed).

Without revision control, I would expect these two operations to be the
same:

- Copy a file over an existing file
- Delete the destination and create a new file with the same name

Now with SVN, it will notice and remember the delete but what harm can
come from silently reverting the delete when someone tries to create a
deleted file?

If the user wanted the delete in the repository, he could have committed
it before the copy. If not, the two operations should be equal for all
cases that I can imagine.

It also shouldn't be hard to do because you already notice the problem
and show an error.

Another solution: Show a dialog which gives the option "Forget about the
delete" and "Continue". But I really can't see why someone would like to
abort what he's currently doing because of this error.

-- 
Aaron "Optimizer" Digulla a.k.a. Philmann Dark
"It's not the universe that's limited, it's our imagination.
Follow me and I'll show you something beyond the limits."
http://www.philmann-dark.de/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org