"Mark D. Baushke" wrote: > > vik <[EMAIL PROTECTED]> writes: > > > I searched for and found a post on exactly this same topic on this > > group, and though it was helpfull, I couldnt figure out the technical > > details. So could someone please help me out? > > > > I am looking for a way to require a certain cvs log format > > --per branch--, For example, I want to require a format like "Bug Id: > > <digits>" in our production release branch, but not in the main branch. > > Here's what i found in the other post i read: <SNIP> > The verifymsg script for your module is run once per directory after the > commitinfo script is run. For client/server operations, it is run from > the server-side directory that contains a copy of your files that are > being committed. > Would Vik be able to use the same routines as cvs_acls (a commitinfo script, that comes with the cvs source code) uses, or is the branch passed into the commitinfo script? It sounds like Vik wants a 'verifymsg_acls' in the end anyway, may as well start with code that has already had some serious debugging for a similar purpose. -- Todd Denniston Crane Division, Naval Surface Warfare Center (NSWC Crane) Harnessing the Power of Technology for the Warfighter
_______________________________________________ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
