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

Re: [Subclipse-users] Subclipse 1.1.6 Released

From: Mark Phippard <markp_at_softlanding.com>
Date: 2006-09-19 18:40:04 CEST

Zach Bailey <zach.bailey@hannonhill.com> wrote on 09/19/2006 12:36:56 PM:

> Great work on 1.1.6. I am enjoying all the great performance
> improvements and bugfixes.
> One thing I noticed with the new incoming change set feature - it
> appears when a file is removed in a commit - the change set revision
> that is selected for that is the revision where the file is added.
> That is,
> 1.) File "Hello.java" is added at revision 168
> 2.) File "Hello.java" is removed at revision 250
> 3.) Incoming changeset shows removal at revision 168 with the comment
> from that revision instead of rolling it into the changeset with any
> other changes that may have been made at revision 250.
> Does that sound like a bug to you? Shall I file it in the issue tracker?

That is a known issue. Subversion does not give the proper last changed
revision for an incoming delete so there is no way to know the right
revision. I have a colleague working on a patch for Subversion to fix

It isn't necessarily the revision when the file was added, it is just
whatever revision you have loaded in your workspace.


To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Tue Sep 19 18:40:24 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.