[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

commitinfo and file content

From: Chad Miller
Subject: commitinfo and file content
Date: Sun, 17 Dec 2000 11:35:53 -0500
User-agent: Mutt/1.1.2i

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
  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

(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 <address@hidden>   URL:   (GPG)
"Any technology distinguishable from magic is insufficiently advanced".
First corollary to Clarke's Third Law (Jargon File, v4.2.0, 'magic')

reply via email to

[Prev in Thread] Current Thread [Next in Thread]