Comments on: Subversion sparse checkouts

By: admin

Wed, 21 Sep 2011 09:07:18 +0000

I can’t see why not, if you check out the parent directories to at least that depth before trying to. But I guess one should test this 🙂

]]>

By: Sriram

Tue, 20 Sep 2011 17:50:54 +0000

TortoiseSVN 1.7 has sparse checkouts. It is very easy to use. However the question is, will we be able to add stuff (files/directories) into the omitted directories in the future?

]]>

By: smulcahy

Thu, 07 Jan 2010 12:28:06 +0000

Hi Stas,

Thanks for your comment. The bevaviour of subversion in this case seems reasonable to me – you are tagging the project – not just the part that an individual developer can see.

-stephen

]]>

By: Stas

Wed, 06 Jan 2010 15:54:14 +0000

Hi,

What about the problem of tagging a sparse dir ?
Suppose I have this structure:
myproj
dA1
…
dB1
…

I want user A to work on dA1, and user B – on dB1.
But both are contributing to the same release, let’s call it rel_X.

So, user A builds sparse working copy of myproj
% svn co $SVNROOT/myproj -–depth empty myproj
% svn update -–depth infinity myproj/dA1

.. possibly modifies it in some way and tries to tag:

% svn mkdir $SVNROOT/tags/rel_X
% svn copy myproj $SVNROOT/tags/rel_X/ -m “tagging my part”

The problem that we see is SVN for some reason also copies dB1 under $SVNROOT/branches/rel_X !!
% svn ls $SVNROOT/tags/rel_X/myproj
dA1
dB1 <- this should not be there !

Any ideas ? (SVN version: 1.6.2 (r37639) )

thanks !
Stas

]]>

By: Adrian Smith

Fri, 17 Apr 2009 11:18:40 +0000

Good explanation. I’ve had this problem loads of times. Nice to know this option is there now.

]]>