Benjamin Pflugmann wrote:
> Hi,
>
> On Fri 2008-09-26 at 09:29:56 -0400, C. Michael Pilato wrote:
>> Ian Brockbank wrote:
>>> Hi,
>>>
>>> Is there any sort of advisory depth property for directories so you can
>>> set the default level at which that directory is checked out? Something
>>> like
> [...]
>> I've considered this enhancement in the past, but I usually find myself back
>> at "If most folks don't need the deep stuff in the tree, maybe that stuff
>> should go live elsewhere in the repository and be explicitly checked out by
>> folks that care." That said, I'm not opposed to this advisory depth
>> property idea.
...and in fact, the real feature I think you're looking for here is a more
generic viewspec support, where when checking out you tell your client to
flesh out a working copy as described by some viewspec (and then, if you
want to override the depths later using 'svn update --set-depth', you can).
> A little comment from a bystander: I immediately thought that property
> would probably be nice to have in order to use it on the /tags and
> /branches dirs (and maybe / itself), as accidently checking out all
> there is, is a common beginners error.
>
> Just thought I mentioned a use case which doesn't question the
> repository layout. (And yes, I realize that use case by itself doesn't
> justify the feature at all.)
This, however, is another useful scenario. Of course, here again we don't
get the full benefit unless we can implement this in such a way that the
server only sends what the client needs -- a simple client-side filter would
help only in final disk consumption, but wouldn't do a thing for the high
cost of sucking N copies of your project over the wire via a sloppy checkout
of /tags.
--
C. Michael Pilato <cmpilato_at_collab.net>
CollabNet <> www.collab.net <> Distributed Development On Demand
Received on 2008-09-26 16:28:59 CEST