Re: Res: How to checkout only the tree structure of a repository
From: Blair Zajac <blair_at_orcaware.com>
Date: 2006-11-05 19:19:02 CET
You can use
http://svn.collab.net/repos/svn/trunk/contrib/client-side/
which I wrote for repositories what when checked out would be several
Regards,
-- Blair Zajac, Ph.D. <blair@orcaware.com> Subversion training, consulting and support http://www.orcaware.com/svn/ On Nov 4, 2006, at 3:34 PM, Alex Lopes Pereira wrote: > Ryan Schmidt, > A very common situation in my company is: > I - We want all people to contribute to store important > informations on the repository; > II - We have some rules to classificate all the files that might be > stored. In such a way, that everybody following those rules would > put that file in the same folder. > III - The repository has a big tree structure, more than 10 levels. > > A - People seek over the tree structure to find the correct place > to put a file and even create another sub-folder. It would be a > nice feature that they could seek over the tree structure of a > working copy without wainting 30 minutes to checkout all the files. > B - People don't know if the file is shared in the repository, but > with those rules (II) they know the exactly sub-folder it should > be. Then, if we have a tree structure an efficient and straight way > to get that file is to checkout all the contents of that sub-folder. > > There are some other situations that I could post here. > As much as I understood until now there is no way to checkout a > working copy containing only the tree structre. Then, a quite > similar solution would also help me: Checkout only the smallest > file of every folder in the tree structure. Is it possible?? > > Thanks, > Alex > > ----- Mensagem original ---- > De: Ryan Schmidt <subversion-2006d@ryandesign.com> > Para: Thomas Harold <tgh@tgharold.com> > Cc: Subversion List <users@subversion.tigris.org> > Enviadas: Quarta-feira, 25 de Outubro de 2006 0:35:20 > Assunto: Re: How to checkout only the tree structure of a repository > > On Oct 24, 2006, at 22:18, Thomas Harold wrote: > > > The issue arises in more complex repositories (ours has 500+ > > projects spread across a few dozen clients). As an administrator, > > the idea of creating 500+ projects is a nightmare. Even having one > > repository per client would be difficult (we add clients all the > > time, I don't want to be the bottleneck for setting up new > > repositories). > > > > As a user, trying to get a single file X/XYZ/123.txt quickly is > > also a nightmare, especially if I have to create a new working copy > > or create all of the folders between the root folder of the > > repository and the folder that contains 123.txt. > > I don't understand why you want the intermediate folders. What's > wrong with something like: > > svn co $REPO/X/XYZ X-XYZ > > ? I often did this for our repository which also had a client>project > hierarchy. > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org > For additional commands, e-mail: users-help@subversion.tigris.org > > > > Yahoo! Search > Música para ver e ouvir: You're Beautiful, do James Blunt --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org For additional commands, e-mail: users-help@subversion.tigris.orgReceived on Sun Nov 5 19:20:23 2006 |
This is an archived mail posted to the Subversion Users mailing list.
This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.