Doug Musinger wrote:
>~
>"/tmp/cvsU8Y8FX" 19L, 528C written
>cvs server commitinfo16 no such user variable ${=MSG}
>cvs server commitinfo17 no such user variable ${=MSG}
>cvs server commitinfo18 no such user variable ${=MSG}
>cvs server commitinfo19 no such user variable ${=MSG}
>cvs server commitinfo20 no such user variable ${=MSG}
>cvs server commitinfo21 no such user variable ${=MSG}
>cvs server commitinfo22 no such user variable ${=MSG}
>cvs server commitinfo23 no such user variable ${=MSG}
>cvs server commitinfo24 no such user variable ${=MSG}
>cvs server Pre-commit check failed
>cvs [server aborted] correct above errors first!
>cvs commit saving log message in /tmp/cvs7p8hYX
>[acme@repo doc]$
It looks like your commitinfo script(s) is/are failing. Maybe because
there's a bug in it. Who wrote the script?
The "commitinfo" file is used to control pre-commit checks. It
specifies a filter program to run for specific directories. A
non-zero exit of the filter program will cause the commit to be
aborted.
This explains why you can do everything but commit.
--
Stephen Rasku E-mail: [EMAIL PROTECTED]
Senior Software Engineer Web: http://www.pop-star.net/
TGI Technologies
_______________________________________________
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
