If I remember correctly, the script run from commitinfo should be able to
find the referenced files in `pwd`.
Derek
--
Derek Price CVS Solutions Architect ( http://CVSHome.org )
mailto:[EMAIL PROTECTED] OpenAvenue ( http://OpenAvenue.com )
--
I will not fake seizures.
I will not fake seizures.
I will not fake seizures...
- Bart Simpson on chalkboard, _The Simpsons_
Chad Miller wrote:
> Hi, all.
>
> Cederqvist notes in sec C.4 that commitinfo can be used to enforce coding
> standards, but I've yet to find any example of how one might do that.
>
> I've come up with the program that commitinfo references using RCS
> directly,
> co -p $file+",v"
> , but that seems awfully ugly (and not exactly correct). Does anyone
> have working code to show of commitinfo peeking in the files to be
> committed?
>
> (My particular goal is to use CVS to keep named's zone files, and ensure
> parsability during commit, so after a commit I can export a new tree, and
> refresh DNS info without worrying about bad files.)
>
> - chad
>
> --
> Chad Miller <[EMAIL PROTECTED]> URL: http://web.chad.org/ (GPG)
> "Any technology distinguishable from magic is insufficiently advanced".
> First corollary to Clarke's Third Law (Jargon File, v4.2.0, 'magic')
_______________________________________________
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
