[Subclipse-users] Re: subclipse / renaming file twice with no commit in between loses revision history

Mark Phippard wrote:

> Yes this is a well known limitation in Subversion itself. Well
> technically the Subversion limitation is that the second move will
> throw an error. We have a workaround in place where we detect this
> and just add the new file. It is not so much to deal with this
> specific use case but more common ones like renaming a folder and then
> a file in the folder.

By the way, can this workaround be disabled? I'd rather be forced to
commit between renames (or, more commonly revert the first rename) than
loose history.

Regards,

Andreas

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Mon Dec 3 23:17:35 2007