[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Wed, 03 Oct 2001 05:26:19 GMT
CVS documentation ( Cederqvist ) claims that commitinfo can be used "for
instance, to verify that the changed files conform to to your site's
standards for coding practice." But try as I did, I could not find
single line telling how to do it?
The script/code listed in commitinfo is invoked with directory path and
names of files just before they are to be checked. But how can I access
the actual file to verify that it is 'conforming' ?
What I am looking for is a method which will be triggered on checkin
attempt of any *.f file and verify that it does not contain lines which
are allowed only in *.F files (like #include #ifdef, etc)
Need help, Tadeusz, 2001/10/03