Following the discussion in the users@ mailing list with the same title, I'm creating this enhancement request. For reference, here is the initial message: http://mail-archives.apache.org/mod_mbox/subversion-users/201311.mbox/%3C527773EC.5050802%40free.fr%3E Basically, I'd like to prepare a working copy for a system that will do the final svn update and over which I have no control. As a result, I'd like to avoid, if possible, that this final update does nothing. This is why I propose to add the "--record-only" option to "svn update --set-depth" This would most useful with external (and unmodifiable) systems that behave this way: If working copy does not exist, do a checkout If working copy exist, do an option-less update With the above option, it would be possible to prepare a working copy with the appropriate depths set while not actually retrieving the data, and thus saving bandwidth and time.
Original issue reported by obones