I am sure this is the intended behavior, but I wish it wasn't.
When you run the command:
svn update -r N
The command will set every file in the WC to revision N even files that are
at a higher revision. In my opinion, the command should only update the
files and folders that were at a lower revision than N and leave the other
ones alone. The switch command could always be used if the whole WC needed
to be at a specific revision, and update could also support the --force
option as well.
Why?
In Subclipse we have this "Synchronize" view that lets you graphically
Synch your WC with the repository. This might include graphically merging
changes manually etc... Anyway, for correctness, we have used update -r N
to perform updates so that if additional commits have been made since the
process started the user does not receive any unexpected updates.
The problem is that if a user does a commit before they do updates, then
when they come back and do an update at their root folder, the update
process removes what they just commited from their WC. We cannot just
update the revision based on the commit because to do that you would really
have to just rerun the whole process, which from a performance point of
view is not desirable.
Just venting I guess.
Thanks
Mark
_____________________________________________________________________________
Scanned for SoftLanding Systems, Inc. and SoftLanding Europe Plc by IBM Email Security Management Services powered by MessageLabs.
_____________________________________________________________________________
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Feb 25 21:45:20 2006