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

Re: [Subclipse-users] 0.9.106: File lost after update

From: Mark Phippard <markp_at_softlanding.com>
Date: 2006-02-27 16:54:39 CET

Elmar Fasel <Elmar.Fasel@artnology.com> wrote on 02/27/2006 10:00:54 AM:

> Mark Phippard wrote:
> > > And when I update these, I expect to get HEAD.
> >
> > That is not how it currently works, but is basically what I am
> > proposing. Obviously if everyone expected it to work in one specific
> > way there would be no issue. Unfortunately I think most people would
> > expect to get what they see in the view.
> I had - another :-) - discussion about this behaviour with my
> We have two suggestions how to "solve this issue":
> 1. Make the update "target" configurable.
> - Update to revision determined during synchronize (current
> - Update to HEAD (new behaviour)
> and/or
> 2. Check if the revision determined during synchronize is still the
> highest revision. If not (the repository is "newer" than displayed in
> the synchronize view) popup a message box, saying something like
> "repository has changed in between - do you want to refresh the
> synchronize view?".

Thanks the approach I decided on was that if you specifically select a
folder or the project it will update to HEAD. If you select specific
revisions, than the current behavior of updating to the highest selected
revision will be used.


Scanned for SoftLanding Systems, Inc. and SoftLanding Europe Plc by IBM Email Security Management Services powered by MessageLabs.

To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Mon Feb 27 19:07:38 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.