Bryce Ready wrote:
> I was excited to use the new 'Sparse Checkout' feature. I administer a
> repo that is big with lots of data, and I want to be able to check out a
> few toplevel directories and then 'drill down' to fix things only where
> I need them.
> When I did a fresh checkout of the root of my repository, using the
> "immediate children, including folders" option, it took the better part
> of an hour. Judging by the number of bytes transferred, my entire
> repository was downloaded and discarded, except for the immediate
> children of the repository root. Every time I want to "drill down," I
> have to essentially do the same thing over again (at least for the first
> few steps). Since my repo structure doesn't branch out widely for
> several steps, it will take me several hours to construct my desired
> sparse working copy.
> It would sure be nice if I could quickly (as in downloading only the
> actual folders that will end up in the working copy) perform this kind
> of checkout. Is there a reason why the entire fully recursive file tree
> must be downloaded and most of it discarded (if that is indeed what is
If your repository is pre-1.5, then it won't know about the new feature,
so 'filtering' what to send doesn't work. The filtering then has to be
done on the client side: that's why still your whole working copy is
downloaded, not just the ones you've specified.
Once you upgrade your server to 1.5, the sparse checkouts will be *much*
faster and really only download what you expect.
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.net
Received on 2008-07-11 08:41:04 CEST