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

Re: Behavior of update command

From: Mark Phippard <markp_at_softlanding.com>
Date: 2006-03-01 02:29:38 CET

> Ah, I see, the value of N is the same in both updates because the
definition of
> it is only the highest such number that was cached locally in the earlier
step
> (when "Synchronize" was chosen and a "status -u" was performed), and this
cache
> hasn't been updated to account for the commits that were performed in the
mean
> time.

Yes, that is it exactly.

> You're back to the problem of specifying exactly what you want
conceptually.

I do not know if I want anything, I mainly just need to write it out for my
own benefit although the discussion has been helpful. If I did want
something, then I would want a way for:

svn up -r N

to not update any files or folders that are > N, just the ones that are <
N.

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 Wed Mar 1 02:30:36 2006

This is an archived mail posted to the Subversion Dev mailing list.