On Nov 3, 2006, at 14:01, Thomas Harold wrote:
> Let's go with the simple case and say that a developer is working
> on project A, B, D and F for a particular client. In order to make
> life simple, they would cloak C, E and G so that they could do a
> "get latest" (similar to "svn update") at the customer level which
> would then update their local working copy for all 4 projects.
>
> In the SVN world, they have to individually do updates separately
> on A, B, D and F project folders, or simply bring down projects C,
> E and G as well. (Or they could write a batch file to do "svn up"
> in each project folder...)
>
> It's always been a client-side setting (developer B won't want the
> same cloaks as developer A) in the VSS world. It's more of a
> convenience feature then part of the development process, but it
> makes working with large and complex repositories a lot easier.
>
> I can envision that some users would even like the ability when
> doing a checkout to say "cloak all sub-folders by default". Then
> they can pick and choose which folders to bring down locally. (But
> that's a "far out" use case and not very typical.)
Sounds like the feature Subversion calls "non-recursive checkouts".
http://subversion.tigris.org/issues/show_bug.cgi?id=695
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat Nov 4 03:17:36 2006