[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 13:05:27 CET

Aaron Digulla wrote:

> - 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.

Open issue here: Imagine two users A and B. File X in the repo is newer
than their working copies.

A runs synchronize
B runs synchronize
A commits file X
B updates file X

What will B expect to get?


A runs synchronize
B runs synchronize
A commits file X
B updates file X
B changes file X
B commits file X
A updates dir of file X

(note: both users run sync just *once*).

Will A expect the file to change?

Maybe the only solution is to go back to individual updates but to group
them by revision numbers:

- Remember the highest revision number during population the sync view.
- For all files which are committed individually, remember the highest
rev for them. Don't touch the revs for the other (incoming) files.
- For all incoming changes, update to the number we got during the
population step. This includes directories but not the files in them
(non-recursive update).

Another solution: During sync, request an actual update but don't apply
it, yet. Apply the parts of the update individually when the user
requests it.


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."
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Sun Feb 26 13:06:01 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.