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

Re: How to checkout only the tree structure of a repository

From: Thomas Harold <tgh_at_tgharold.com>
Date: 2006-10-25 05:18:58 CEST

Sheryl wrote:
>> That would be a nice feature, especially on larger repositories where
>> users only want to work on a small sub-section and only need to download
>> specific folders or files.
> But checking out from the top of the tree isn't a requirement, is it? I
> haven't needed that yet, but I was under the impression that a person
> could checkout from any place in the tree -- not just from the top.

The issue arises in more complex repositories (ours has 500+ projects
spread across a few dozen clients). As an administrator, the idea of
creating 500+ projects is a nightmare. Even having one repository per
client would be difficult (we add clients all the time, I don't want to
be the bottleneck for setting up new repositories).

As a user, trying to get a single file X/XYZ/123.txt quickly is also a
nightmare, especially if I have to create a new working copy or create
all of the folders between the root folder of the repository and the
folder that contains 123.txt.

If SVN allowed us to say (from a folder that already is a working copy):

svn up X/XYZ/123.txt

Where it would automatically create the sub-folder X, then the
sub-folder XYZ, then pull down just the 123.txt file; then things would
be ideal.

I'd even settle for pulling down everything in the XYZ folder. So long
as I don't have to create sub-folder X and XYZ by hand.


The specific use case is someone who doesn't have the entire repository
downloaded to their working copy (and doesn't need to), who only wants
to get a file/folder that is 2+ folders deep within the tree, without
spending more then a minute getting to the file or files.

Creating a new working copy is an expensive operation in terms of human
time. Especially for less technical users.

Since SVN seems to have difficulties dealing with cases where the local
folder doesn't exist, being able to pull down only the folder tree would
be a reasonable stop-gap measure. After all, once I have the folder
tree down, I can always do an "svn up -N" to get the content of the
folder downloaded.

(I've been round and round about this, looked at TortoiseSVN, QSVN,
RapidSVN, SubCommander, the command-line client. TortoiseSVN actually
comes the closest to being able to do what SourceOffSite or Visual
SourceSafe were able to do easily. All TSVN needs is the addition of an
"update" command in the Repo-Browser that can create the intermediate

Even if SVN were to pull down the contents of the intermediate folders,
that would be okay. As long as it doesn't go on a multi-gigabyte
download spree of all of the other folders that I'm not really
interested in. (So I'm looking for a "deep" update that is very precise
instead of a "broad" update that pulls down the entire world.)

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Oct 25 05:20:09 2006

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.