[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: Aaron Digulla <digulla_at_hepe.com>
Date: 2006-02-26 12:53:57 CET

DM Smith wrote:

>> By the way, I was able to confirm that this is the problem.
>>
>> Maybe when you do a commit we should/could force a complete refresh of
>> the
>> Synchronize view?
>>
> Basically that was what I was suggesting by "invalidating" synchronize.
> Whether or not you update to Head, I think this will still be needed.
> Updating to head would have been the behavior that I was expecting.

As I see it, the problem is a mix of revision numbers (ie. what you want
 to achieve is "update to the latest revision of my branch" and not
"update to revision 100").

So we have these scenarios (in Synchronize):

- Incoming change. Here, you know the base revision (wc) and the new
revision. During update, find the highest revision on the server for the
current branch (it's not be enough to just find the highest rev of all
incoming changes; see below) and update all files/dirs to it.

Caveat: Updating a dir might delete it (and the files in it).

- Outgoing change: When a user does a commit of some files during a sync
run (ie. you have now incoming changes, new revisions due to the commit
and changed working copies which will are not revisions, yet), then
update the highest known revision number after the commit.

So my guess is that you must somehow figure out what the highest revsion
in your current branch is.

From this point of view, I wonder how subversion solves this. What
happens when I checkout a branch and then run svn up in it? What
happens, when I update a branch to the highest revision number on the
server? That can't be the same as updating to HEAD, can it?

Regards,

-- 
Aaron "Optimizer" Digulla a.k.a. Philmann Dark
"It's not the universe that's limited, it's our imagination.
Follow me and I'll show you something beyond the limits."
http://www.philmann-dark.de/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Sun Feb 26 12:54:19 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.