Volnei wrote:
> Hi, Stefan
>
> I was thinking in how could TortoiseSVN help users to do this kind of
> sparse checkout in complex repository structures (where checkout
> individual directories can be exhausting). For instance, in structures
> where there are hundred of branches/tags but where you are interested
> just in few ones. In fact, it’s just an idea in how could TortoiseSVN
> help users to define the repository sparsity automatically to every
> new checkout. See if this would work:
>
> Tortoise could look at a new tsvn property valid only to directories.
> For instance “tsvn:default-depth”, with possible values “empty”,
> “files”, “immediates” and “infinity”. If a checkout is requested in a
> higher level than the directory where the property was defined (for
> instance, in the repository root) TortoiseSVN will behave as if the
> user had used “--depth=” directly just for this directory. If the
> checkout is done in the same level of the directory, TortoiseSVN will
> behave as the user choose in the “Check-out” window.
Such a feature would have to be implemented in the core subversion
library, and I think you won't have much luck with that with the
Subversion developers.
TSVN can't interfere with checkouts, so it doesn't know beforehand which
directories really get checked out, and it can't fetch the properties
before a checkout because of that. And it also can't fetch such
properties during a checkout because that's completely done inside the
svn library.
Stefan
--
___
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.net
Received on 2008-08-03 08:47:18 CEST