Grey-Cells wrote, On 10/15/2008 10:21 AM: I want to verify whether the check-in comments are not null or are in a certain format. I had figured out that verifymsg does the thing for me. I had written
"Re: Verifymsg on branches?"Date: Wed, 22 Nov 2000 15:29:54 has an simple example rcsinfo & verifymsg which I have used on a project to make sure people put in bug numbers and at least simple comment
<SNIP> If you do not have policies that are carved in stone, you may be able to let the programmers work smarter not harder. Instead of attempting to make sure there is a history file in the director
<SNIP> If you want something that is simple, and I mean simple no checking for branches, which makes sure bug ID's are applied, try the verifymsg and rcsinfo combo. for my setup I use something clos
Thanks, I sort of have a similar script. However, I want to force folks to use a certain Bug# when submitting to a certain branch. But I don't see (or I can't parse) any occurrence of the word "Tag".
Getting the bug number is not a problem with rcsinfo and verifymsg, and then validating it can with some command line accessible tool on unix during the verifymsg phase. This command line tool could
For some of my projects, I have defined a rcsinfo/verifymsg set that requires feed back about the review process that the developers are supposed to go through prior to commit. The verifymsg script c
Short answer, Yes. Short answer, Yes. Long answer, search the list and read the manual, specifically on commitinfo and verifymsg. I have sent a few messages[1] over the years to the list on how I hav
Frank Grunwald wrote (using a possibly invalid email address to boot): look at verifymsg[1] and possibly rcsinfo[2] too. If you search the list[3] you might even still be able to find the verifymsg s
address@hidden wrote, On 09/26/2007 02:08 AM: On 25 Set, 22:01, Todd Denniston <address@hidden> wrote: As you use CVSNT you might get answers, we don't know about, by using their mailing lists:http:/
I want to write scripts for loginfo, commitinfo verifylog etc files to check for empty log messages. Check if any branch is created. Multiple branches are created for a perticular file. Label is crea
i'd like to ask whether it is possible: 1- to disallow empty comments in commits and/or Yes, you could write a verifymsg script which denied a commit for which the log message was empty. You would p
<SNIP> Three suggestions other than CVSNT, or posibly even in addition too. 1) implement rcsinfo + verifymsg [1] to make your coders put in appropriate bug/change/SCR information with thier comments.
<SNIP> 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 w
<SNIP> CVS might not do it for you, but you might be able to get some where in between with a combination of $Version: $, commitinfo and a perl (or your favorite scripting language). put @since $Vers
For me, a few times. more interesting was tracking when something that had not worked was fixed and by which set of changes. It could be that most of my repositories were small (<300MB) but I have al
<SNIP> there is no 'default commit template` with cvs, but you can make and use your own following the directions: http://www.cvshome.org/docs/manual/cvs-1.11.14/cvs_18.html#SEC156 specifically the t
--Original Message-- Yep, that's exactly the sort of thing I envisage: a two-part solution Part 1 - Technical - A commitinfo script that disallows any commit unless the log message includes the strin