On Sun, 12 Aug 2018 03:26:38 -0400, Nico Kadel-Garcia <nka...@gmail.com> wrote:
>In practice, I may have a long-term better idea for you. Split the >projects, each into their own much smaller repository with only its >own history. This is also the only good chance you'r likely to get, to >*discard* inappropriate binary files, files that accidentally were >stored with passwords, and seriously obsolete branches.tags, or even >projects altogether. Our SVN repositories are organized in a similar way as the previous CVS repositories were. I migrated the lot back in January and I had to decide on the organization back then. We had about 10 CVS repositories each with a lot of modules (= top level directories). Each repository had different permission settings to allow some employees access while denying all others. To implement a per-project repository in SVN would lead to a management nightmare as far as I could tell, first during migration and second in operation when developers would add their projects to SVN. How could I enforce the permission restrictions in such a scenario? So this is why I have this structure: repository1 |- project1 | |- trunk | |- tags | |- branches |- project2 | |- trunk etc... repository2 |- project1 | |- trunk | |- tags | |- branches |- project2 | |- trunk etc... -- Bo Berglund Developer in Sweden
