1 |
>> I think separate repositories would only be necessary when using |
2 |
>> distributed version control (git) as opposed to centralized |
3 |
>> (subversion). I think subversion's path-based authorization should |
4 |
>> eliminate the need for separate repositories? |
5 |
>> |
6 |
> |
7 |
> Separate repos aren't strictly necessary, but it's much harder to verify |
8 |
> your path permissions than it is to verify that your repositories are |
9 |
> separate. |
10 |
> |
11 |
> The first involves config files and cascading information; the second |
12 |
> involves being able to count to two =) |
13 |
|
14 |
Would multiple repos work in a scenario where different developers |
15 |
have access to different stuff and some stuff should be accessible to |
16 |
multiple devs? I don't think you want the same stuff in more than one |
17 |
repo. It seems like managing multiple repos would get out of hand in |
18 |
that sort of situation and I might be better off with config files and |
19 |
a single repo. |
20 |
|
21 |
- Grant |