> From: Logan Johnson [mailto:[EMAIL PROTECTED]] > Sent: Thursday, December 06, 2001 2:38 PM
> My company has implemented a commit control system, but it is > currently applied by a call from loginfo, which means that the best > we can do is sound an alarm if a commit we don't like goes through. > We need it at loginfo so that we can take into account the log > message, the branch, and the operation on each file involved. Log message can be checked with verifymsg, branch and operation can be checked with commitinfo, although it takes a little extra effort. So I don't see the need for this unless you want to have special requirements for log messages depending on which branch is affected or what operation is being performed. Is that what you're doing? Sorry I don't know enough to comment on your specific question, "unintended consequences." Jerry _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
