RE: Have CVS perform actions on all files before checking in?

[Zieg, Mark]

> > Is it possible to have CVS perform some type of
> > action on types of files
> > before checking it in? I'd like to configure our
> > server for all java and C++
> > code to do some nicetys, like strip out ^M's and
> > replace bloody tabs with
> > spaces where people put them in. 
> 
> Rather than having the commitinfo
> hook modify the files, just have it reject the checkin
> until the files fit the coding standard.

Or have an alias or ~/bin/cvs wrapper script catch "cvs commit" calls and do
your sed, perl, etc stuff there.  That way you can modify the local sandbox
files before they are sent to the repository, and your working copy will
match the new repository version.