On Fri, Jun 15, 2018 at 2:58 PM, James Peng <oldyounggu...@yahoo.com> wrote: > Hello everybody, > > I have the following project structure: > > Project > --.svn > --branches > --p1 > --p2 > --trunk > > Now my co-worker has added a ‘p3’ under the branches and also a > ‘products/pp1’ under the Project folder: > > Project > --.svn > --branches > --p1 > --p2 > --p3 ---------------------- > newwwwwwww > --trunk > --products > --pp1 > ----------------------newwwwwwww > > > How can I get the new p3 and pp1 without get extra .svn under other folders? > > It seems I have to use ‘co’, then I will get .svn folder extra .svn under > other folders. These extra .svn folders should not be there? How to avoid > them?
It depends a bit on how you have set up your working copy. I believe you're looking to have a "sparse working copy" with several parts of the repository (but all being part of one working copy / one working copy root / one .svn folder). If so, I suggest you take a look at: http://svnbook.red-bean.com/nightly/en/svn.advanced.sparsedirs.html Basically 'co' will give you an entirely new working copy, with its own root (it can be embedded in another working copy, but that's not a great idea). If you want to change the "sparseness" / structure of your existing working copy, you need to use 'svn up' in combination with the --set-depth option to include or exclude extra parts. -- Johan