Being able to change the whole source does not mean it is permitted.
I expect everyone with write access to the source understands this
difference, and accept that only the backend maintainer make changes
to his backend.
> Normally there is one person who works on a backend. It is not a
> good idea if anyone has write-access to the backends. If someone
> else wants to change anything on a backend, he should mail his patch
> to the author of the backend.
Exactly. You don't need to block write access using CVS to make this
happend. There only has to be agreement between the people with write
access.
[Kevin Charter]
> Is there a way to give maintainers restricted write access,
> say to just the part of the package they are responsible for?
[Oliver Rauch]
> If we use CVS, that is the only way that makes sense!
Why use technical means when all that is needed is general consencus?
-- ##> Petter Reinholdtsen <## | pere@td.org.uit.no O- <SCRIPT Language="Javascript">window.close()</SCRIPT> http://www.hungry.com/~pere/ | Go Mozilla, go! Go!
-- Source code, list archive, and docs: http://www.mostang.com/sane/ To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com