Re: Refactoring in Eclipse

>> See http://subclipse.tigris.org/issues/show_bug.cgi?id=108
>> In short: It's not a problem with losing the history but a problem
>> with showing the complete history in Subclipse.

Thanks for the hint! Changing to the CLI solved the problem, as it is
described there.

>> BTW, a move in subclipse is equivalent to copy and delete
>> (http://svnbook.red-bean.com/svnbook/re18.html)

OK, good to know. Already from my point of view it does not really
matter. The only important thing that SVN knows after the refactoring
that it is the same resource.

> I find I use the svn status command a lot - it's a very nice quick
> reference for what's changed, and extremely easy on the eye.

At least it is useful until the synchronize repository feature is
implemented in subclipse (which is only an svn -u status command, if I
am not mistaken).

Cheers,

Gabor
Received on Tue Aug 3 17:43:05 2004