It seems as if new error handling code now caused CSSC commands to exit with a non-zero status even for warnings.

E.g. `get` will exit with an exit status of 1 whenever it extracts a file without keywords and gives a "No id keywords" warning:

$ /work/woods/g-cssc/build-x64-netbsd/src/get -p -s -a1 usr.sbin/sendmail/src/SCCS/s.main.c > /dev/null
/work/woods/g-cssc/build-x64-netbsd/src/get: warning: usr.sbin/sendmail/src/SCCS/s.main.c: No id keywords
$ echo $?
1

This is new, and very undesirable, behaviour from how 1.4.0 behaved.

Interestingly neither Heirloom SCCS nor Schily SCCS even bother with the warning for this particular file:

$ /usr/local/heirloom-ccs/bin/get  -p -s -a1 usr.sbin/sendmail/src/SCCS/s.main.c > /dev/null
$ echo $?
0
$ /usr/local/ccs/bin/get  -p -s -a1 usr.sbin/sendmail/src/SCCS/s.main.c > /dev/null
$ echo $?
0