Such a scheme would be very hard to implement if it has to be secure
against an intentional attempt to change something one isn't allowed
to.
If it's not water-proofed anyway and if very few people have access to
the CVS tree, the problem should be solvable by obeying to a
policy. NetBSD does it that way and I never heard about people
committing to anything they wern't allowed to.
Readonly access is no problem anway given cvsup, annoncvs etc.
The most important point (for me) is that currently no history and no
log messages are visible. CVS would solve this, even if only one
person commits.
Martin
-- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin Cracauer <cracauer@cons.org> http://www.cons.org/cracauer BSD User Group Hamburg, Germany http://www.bsdhh.org/- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/