Re: Testing sparse working copy

Dave Lawrence wrote:
> Unless I'm mistaken the following command line sequence cannot be
> emulated from the TSVN gui build 10873
>
> svn co http://repo/ --depth=empty
> svn up proj1 --depth=empty
> svn up proj2 --depth=empty
> cd proj1
> svn up trunk
> cd ..\proj2
> svn up trunk
>
> Basically, the issue is that the update command can specify a path
> that's not yet in the working copy but there is no equivalent operation
> in TSVN.
>
> However, I can report that once this sparse working copy layout has been
> generated, this build of TSVN does work with it fine. I can now do an
> atomic commit in 3 different projects without having to checkout the
> whole repository!

I have to admit, when I first read your report I thought that you're
wrong and that TSVN could deal just fine with sparse checkouts. But then
I could see the problem: it's not possible to get single subfolders once
a checkout with depth empty is done.

So: as of revision 10882, the repository browser (if started from a
working copy) shows a context menu entry "update item to revision..."
for folders which don't exist in the working copy, but their parent item
does exist.
Which means in your example, you would have to start the repobrowser on
'repo', then right click on 'trunk' and choose 'update item to
revision..' which will bring up the update dialog. There you can set the
depth for the update for that non-existing item.

Stefan

-- 
        ___
   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.net
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org