On Fri, Jun 15, 2018 at 10:25 AM, Johan Corveleyn <jcor...@gmail.com> wrote:
> 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. > > I had a couple of different thoughts. 1. SVN client version matters. SVN 1.7+ will have only a single .svn folder at the root of the working copy, but SVN 1.0-1.6 put a .svn folder in every folder. 2. Usage of svn:externals matters. Every svn:external reference is a working copy inside the working copy and it will contain a .svn folder at its root. So that is kind of the exception to the previous point. My assumption is that James is running into one of these issues. -- Thanks Mark Phippard http://markphip.blogspot.com/
