[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: [Subclipse-users] Two consecutive move operations reset resource history

From: David Corbin <dcorbin_at_machturtle.com>
Date: 2006-03-21 05:22:04 CET

On Tuesday 21 March 2006 05:11 am, Toivanen Sampsa wrote:
> Hello!
> I'm a bit confused by Subclipse's behavior when doing two consecutive
> rename/move operations for a single file in Eclipse. For example, when
> renaming first.txt to second.txt and immediately after that to third.txt
> without a commit in between, Subclipse performs the following
> operations:
> move C:/test/first.txt C:/test/second.txt
> A C:/test/second.txt
> D C:/test/first.txt
> add -N C:\test\third.txt
> A C:/test/third.txt
> delete --force C:/test/second.txt
> D C:/test/second.txt
> As a result of the latter explicit add and delete operations, the
> resource history of third.txt is reset i.e. it shows nothing about
> first.txt or second.txt. If, however, a commit was made after renaming
> first.txt to second.txt, the resource history would then be ok all the
> way up to third.txt.
> In my opinion, Subclipse should disallow the second rename operation in
> eclipse, instructing the user to do a commit first.

In *my* oppinion, it should revert the first move, and then do the second
rename as if the first never happened. (I'm sure that's a fair amount of
work, of course, but that creates the best user experience).


To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Tue Mar 21 11:27:10 2006

This is an archived mail posted to the Subclipse Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.