"Bennett, Jason" <JBennett@MainPointSystems.com> wrote on 09/22/2006
02:25:43 PM:
> I am using 3.2, so I'm not sure if you mean that Subclipse needs to take
> advantage of the Eclipse feature or not.
>
> As for the version number, way back when Subclipse used to update to the
> revision number that the sync was done to, so that if you did a Team
> Sync, and someone checked in another commit before your update, you
> wouldn't get the latest. Moreover, if you did a sync, a commit, and then
> an update (wrong procedure, I know), you'd end up rolling back your
> changes locally (although they'd still be in the repository). This was
> changed several versions back so that update always pulled from HEAD, no
> matter when the sync was done.
>
> Subclipse now seems to have reverted back to the old behavior of syncing
> to a given revision number. This is probably because of the change sets,
> but I did prefer the previous behavior.
If you want to update to HEAD, use Team -> Update from one of your
"normal" views like the Package Explorer.
Update from Synch view is greatly improved in this version, especially
when showing the out of date folders. It should now behave more like one
should reasonably expect. Previously we pretty much had to update to HEAD
because it was easy to really mess yourself up and backdate some revisions
if we didn't.
Update from Synch view will update to HEAD if you have selected any
incoming deletes in the view. This is because currently we are not
getting accurate information on the revision where the item was deleted,
so we have to udpate to HEAD in order to update to a revision where the
item was deleted.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Fri Sep 22 20:31:19 2006