news <email@example.com> wrote on 04/19/2005 03:57:34 PM:
> Do you have any idea if this is a lot of work or complicated to do? Or
> would it be better to ask the Subversion team for a "real" rename (which
> is mentioned on the roadmap as 'mid-term'). This should make the problem
> go away since the second rename would restore the filename to its .svn
> state and simply mark it (M)odified if I edited it, just as usual.
> I'm not sure there's much of a point spending lots of time with
> workarounds if the root cause is really Subversion's behaviour.
> I guess I'll just ask on svn-users and see what the devs think.
I do not know how difficult it would be or what the issues are.
Regardless, it is still a problem in that Subclipse tried to do something,
it failed, and you did not know it failed. Perhaps there was an error in
the Console view if you were showing it, but ideally the error should have
rippled all the way back to Eclipse so that the rename did not happen.
Scanned for SoftLanding Systems, Inc. by IBM Email Security Management Services powered by MessageLabs.
Received on Wed Apr 20 22:32:20 2005