[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: [Subclipse-users] does subclipse send the wrong update command or is this just how svn works? (own commit overwritten and then i can update it back in)

From: Mark Phippard <markphip_at_gmail.com>
Date: Wed, 1 Dec 2010 08:48:50 -0500

On Wed, Dec 1, 2010 at 8:23 AM, jcompagner <jcompagner_at_gmail.com> wrote:
> And what i really want in the synchronize view update
> "update C:/workspace_trunk/j2db_server -r 30052 --force"
> i really want to get only the files that are really in THAT revision
> and nothing more..

That is not how update works. The issue is likely that your project
root folder had an incoming change (probably svn:mergeinfo property
changed). Since the folder was updated, so were the children and they
will all be updated to the revision specified.

I would expect if you refreshed your Synch view the revision of that
folder might have jumped up to 30054 and this would not have happened.
 We have that preference that is now off by default called something
like "Show Out of Date Folders". When this is on, after a commit the
Synch view is refreshed automatically. Most people do not like this
feature because it adds a lot of noise to the view. But it has the
benefit of keeping your working copy in synch better.

Mark Phippard
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subclipse.tigris.org].
Received on 2010-12-01 14:49:02 CET

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.