In article <[EMAIL PROTECTED]>, Mark A Flacy (maf) writes:
Richard> I can't, so far as I can see, use file permissions, users need write
Richard> acess to the repository to make lockfiles etc all over the place.
maf> That's not the same as giving them write permission on the individual files.
But if I start some policy of controling individual file permissions
it means some poor sod has to make sure every file checked in has the
right permissions, or a regular process does. Yeuch.
And if they can write the directory to make a lock file/directory they
can presumably check in new files and who knows what else might sneak
through.
If CVS created it's lock files outside the repositary itself, then
simple access controls on the whole repository would work and that
would be much cleaner. Then I could put each module directory in the
repository into it's own group and control access that way.
--
Mail me as [EMAIL PROTECTED] _O_
|<
_______________________________________________
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
