[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-26 14:39:12 CET

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

No, that is not really the issue. Branches do not have their own revision
numbers, when a commit is done anywhere, the entire repository has its
revision updated. So your branch has a "state" at every possible revision
number, it is just that at many of those revisions there are no
differences. In other words, if revision 100 is the last commit to your
branch, but the current HEAD of the repository is revision 110, then
updating the branch to r100 and HEAD results in the same output. Although
the latter option is better because then the folders are all updated to
HEAD (r110) which is necessary for a prop-change or delete to be performed.

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


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 Sun Feb 26 14:39:34 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.