On Thu, May 9, 2013 at 12:16 AM, Amit Kumar [IN7537] <amit_ku...@mindtree.com> wrote: > > Thanks for reply. But in my condition there are 77 items are in parent folder > which is group of project and some other folder like image location, document > location. All project folder is required except like documents and image > folder. > so I have to check out from parent folder only. Sometimes other team create > new project. If I take full update then only all project will come in my > local or all will update including new project. > I want to lock some folder and then I want take full update and I want to > update only project folder.
I see others have described how to get a sparse working copy but personally I'd rearrange the repository layout to match the structure so you can check out one top level directory and get what you want. If that is the way everyone uses the repository, perhaps you could move the 77 things you want under a new upper-level directory parallel to the one you don't want. Or, if everyone uses different parts, group them under directories that match the use patterns, then add a new directory that you check out containing svn externals that pull the other components into the right places and others can do the same for their own layouts. The bad (or good, depending on your use patterns and tools...) side of externals is that commits don't automatically recurse into the folders pulled through external references. Checkouts and updates follow them automatically, but you have to explicitly commit changes separately. Externals also make it much easier to work with separate trunk/branches/tags folders at project-level folders for various components with separately-managed component releases, but it doesn't sound like you are using that convention in your repository now. -- Les Mikesell lesmikes...@gmail.com