> Hello All, > > I am trying to implement a process where in > > 1) A developer checks in a file[s] against a valid defect ID, This > transaction is captured in a database with the bugid , userid date and the > file list checked in for this bug. > Do you want to abort the checkin if there is something wrong, or just capture the transaction? Where I last worked, I was going to implement verifymsg to force people to put PR numbers (we used Gnats for error tracking) in the log messages, but no more checking than that. > 2) My problem is verifymsg hook has the log message where I can verify that > the bugid is entered and is valid, but does not have the file list. By this
The hooks are set up in a somewhat ad hoc manner. You could set up loginfo to get the file list, the new revision numbers, and the log message, and enter that into the database. IIRC, loginfo programs are run once per directory, not once per commit, so there will be multiple entries for larger commits, but I don't know that that's going to be a problem. David H. Thornley | If you want my opinion, ask. [EMAIL PROTECTED] | If you don't, flee. http://www.thornley.net/~thornley/david/ | O- _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
