[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 14:54:09 CET

Mark Phippard wrote:

> The issue is that updating to HEAD is the easiest thing to do, but it does
> have a potentially negative side effect that if commits have been done to
> your project since you opened the Synch view, then updating to HEAD is
> going to include those commits even though they did not appear in the Synch
> view.

So the actual problem is that updating to the latest revision (which
isn't HEAD; HEAD is a special branch) will cause to include commits
which happened after the sync view was populated.

Would it be possible to collect the updates without applying them (like
"Create Patch")?

Or you need to get the highest revision number of all files in the sync
view (excluding those which were committed in the same view). During an
update, you have to check if there is a committed file in the current
subtree. If so, you have to do the update manually for each file.

After sync, you should have a list of files to consider, so this step
might not be as expensive as it sounds.

In fact, what we need to achieve is "update everything in this subtree
*except* the files which were just committed". How about an
"exclude"-option in svn up?


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 14:54:43 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.