[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: Directory cloaking

From: Gavin Lambert <gavinl_at_compacsort.com>
Date: 2005-11-06 22:27:12 CET

Quoth Robert Swarbrick <mailto:robert.swarbrick@asg.com>:
> Rather than simply checking out svn://myserver/software/trunk
> as a whole, check it out non-recursively, then individually
> check out the sub-folders you want on that client.
> svn checkout -N svn://myserver/software/trunk config1 cd config1
> svn checkout svn://myserver/software/trunk/projectA
> svn checkout svn://myserver/software/trunk/projectB
> svn checkout -N svn://myserver/software/trunk/groupC cd groupC
> svn checkout svn://myserver/software/trunk/groupC/projectD
> svn checkout svn://myserver/software/trunk/groupC/projectF

If someone has already done a full checkout, is it possible to "discard"
a folder retrospectively?

I'm thinking that removing the folder at the OS level and then manually
tweaking .svn/entries in the parent folder would do the trick. Is that
correct, or will that just break stuff?

> This does mean that if someone adds in "projectF2" to
> "groupC" you won't get it automatically, but given your
> requirement of "different machines/developers need different
> code" that's presumably desired.

Yep, exactly.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sun Nov 6 22:29:15 2005

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.