[cvsnt] Re: Commitinfo trigger script data?

[Tony Hoyle]

John Kinson wrote:

> I would like to be able to run some tests on files being committed, and 
> abort the commit if the tests fail.  Reading the documentation, the 
> commitinfo trigger point seems ideal, but I can't figure out how to 
> access the revisions being committed: the only information supplied to 
> the commitinfo script seems to be the names of the module and files 
> affected.

The script starts in the server temporary directory, which has CVS 
control directories for each committed directory.

loginfo is better for this kind of thing though as that's called for 
each directory.

Tony