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

RE: Re: Re: Fully recursive update is not full

From: Paul van der Hulst <paul_at_piak.nl>
Date: Tue, 13 Dec 2011 02:06:33 -0800 (PST)


Read it, but I don't get how I misunderstood.
Is fully recursive not the same as infinite depth? I assume it is, since tortoisesvn has no infinite option.

What I want to do is --set-depth infinite on the root folder of my working copy. I do this by selecting update... , fully recursive, sticky.
From the doc page you referred to I extrapolate that this should set the depth of the root folder (and because it is 'recursive' also the child folders) to infinite. Because it is applied to the root, and is recursive, all the folders in the working copy, including the root should have their depth property overwritten with 'infinite'.
Afterwards, an update should get me the same contents as a default fresh checkout.
Apparently this is not the case and the documentation does not answer this in a way I can understand.

Instead of understanding what I'm doing wrong, perhaps it is better to find out what I should have done.

Assume I have a working copy which has some files excluded. Assume I don't know exactly which files are missing (or there are so many, naming them all is impractical). How this happened is a matter of history and should not matter, all I want to do is change this selective checkout into a fully recursive checkout. A new checkout is also impractical due to the size and network bandwidth.

How can I check if the working copy is missing files compared to the repository?

How can I restore those files without doing a full checkout?

Best regards,



To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2011-12-13 11:06:42 CET

This is an archived mail posted to the TortoiseSVN Users mailing list.