Hi all,
After playing with cvs_acls.pl and commitinfo for a while, I finally
know how to set up an access control list for the CVS repository.
Access can be granted by files/directories or by branches (or both):
I could say, I want Pete to be able to work on AegisVM/interpret.c but
not other files, or I want Chris to be able to work on a certain
development branch (or some combination of such things). So, what do you
think is the most convenient way to do this. Should I create a separate
branch for each subproject (e.g. a branch for developing
java.lang.reflect, and another branch for developing floating point
arithmatic)? Or should I just limit your access to the set of files
you need to work on? Which is more convenient for you?
Or, do you think it is sufficient just to archive the commit logs in
a mailing list, and forget about the whole access control idea?
I think the criteria should be that the setup should be convenient
for you to work, and also give me peace of mind so I can sleep tight
at night. :-) Please offer feedback.
Philip
* Philip W. L. Fong
* pw...@us...
|
