Re: How not to recurse into specific directories?

[Ryan Schmidt <su...@ryandesign.com>]

On Sep 29, 2005, at 21:10, Michael Ehlers wrote:

> Is there any possibility to set something like a "no recurse beyond  
> this level"-flag in a directory. For example, suppose i'd like to  
> store a lot of projects into one repository:
>
> root
> +----- webapps
> |       +- glover
> |       +- chumani
> |
> +----- guiapps
>         +- challenge
>         +- mydiff
>
> What i want is that on an update to root, all new projects appear  
> in my working directory but not the contents of the folders like  
> "glover". They only appear if i explicitely update "glover", for  
> example.

It's not meant to be used that way.

Instead, you should get a working of each area that you want to be  
able to update separately. For example, get a working copy of glover,  
another of chumani, another of challenge, etc. Arrange these working  
copies in any directory structure locally that makes sense to you— 
either the same way as it is in the repository, or any other way.  
Then issue update commands on these separate applications as needed.

Of course, this way, you cannot in a single revision commit changes  
made across multiple applications. But if that is something you are  
wanting to do, then one wonders whether they should really appear to  
be separate entities in the repository...



---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org