On Mon, 13 Nov 2017 23:10:45 +0100, Stefan Sperling <s...@elego.de> wrote: >If your 6 projects could ever be expected to merge code from one another, >it makes sense to put them all in a single SVN repository because merge >tracking occurs on a per-repository basis (because SVN is not a distributed >version control system). Also, if you wish to use 'file externals' between >projects, they will have to be in the same repository (this is an unfortunate >implementation quirk). >
OK, I will probably just make one SVN repository and make the current repositories top level directories in that repo. Then I can make the path-dependent permissions as described earlier. But now I have to deal with 6 different CVSROOT directories too... Is cvs2svn using the CVSROOT directory during conversion or can they be removed from the source so as not confusing the operation? Or do I need to use the cvsnt cvs.exe during conversion and does that in such a case need these admin files in CVSROOT? I will make a copy of the active repo for use during conversion of course so I can take out the CVSROOT directories if they are not used. -- Bo Berglund Developer in Sweden
