CVS

Is it possible to make the affected directories read-only ?

Mehdi

Derick Rethans wrote:

Hello Folks,

I just shutdown the CVS server because there are still no diffs being
send out. This means that there is no control over who commits what
anymore resulting in the probability of bad code into CVS. Until the CVS
commit mails work again the CVS will remain down. This problem does not
seem to affect all modules though, and also not always.

regards,
Derick

Is it possible to make the affected directories read-only ?

Mehdi

Derick Rethans wrote:

Hello Folks,

I just shutdown the CVS server because there are still no diffs being
send out. This means that there is no control over who commits what
anymore resulting in the probability of bad code into CVS. Until the CVS
commit mails work again the CVS will remain down. This problem does not
seem to affect all modules though, and also not always.

regards,
Derick

Is it possible to make the affected directories read-only ?

Mehdi

Derick Rethans wrote:

Hello Folks,

I just shutdown the CVS server because there are still no diffs being
send out. This means that there is no control over who commits what
anymore resulting in the probability of bad code into CVS. Until the CVS
commit mails work again the CVS will remain down. This problem does not
seem to affect all modules though, and also not always.

regards,
Derick

 I've reenabled cvs access.

 Please send me the complete output of "cvs commit", if you
 receive warnings about uninitialized variables at the end.

 - Sascha