[Top][All Lists]

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

RE: verifymsg and branches

From: Christopher.Fouts
Subject: RE: verifymsg and branches
Date: Mon, 28 Mar 2005 10:19:21 -0500

Hey cool, you mind sharing that script? :)

As far as deleting the stored info, would it be safe
to delete via script run in loginfo, since by then,
the commit is already passed and verifymsg should not
be called anymore?


>-----Original Message-----
>From: Matt Doar [mailto:address@hidden 
>Sent: Friday, March 25, 2005 12:16 PM
>To: Fouts Christopher (IFNA MP DC); address@hidden
>Cc: Matthew Doar (StF)
>Subject: RE: verifymsg and branches
>Thanks, I see we are after similar things. I followed Mark 
>Baushke's suggestion and wrote a script which parses 
>client-side CVS/Entries files (a la cvs_acls) to find out 
>which branches are being affected by the current commit, and 
>then record this information in /tmp for the verifymsg 
>invocation of the same script to use. 
>The only remaining problem is that you don't know when it's 
>safe to delete the stored information, since you don't know 
>when verifymsg is calling the script for the last time. 
>Currently, I'm just cleaning up the files once a night. I see 
>that activitymail records committed filenames to work out when 
>it is being called for the final time, but that's overkill here. 
>> -----Original Message-----
>> From: address@hidden
>> [mailto:address@hidden 
>> On Behalf Of address@hidden
>> Sent: Thursday, March 24, 2005 12:27 PM
>> To: address@hidden
>> Subject: RE: verifymsg and branches
>> Google for the "verifymsg script" thread on suggestions
>> how to get the "branch name" during a commit for the
>> verifymsg.
>> >-----Original Message-----
>> >From: address@hidden
>> >[mailto:address@hidden
>> >] On Behalf Of Matt Doar
>> >Sent: Thursday, March 24, 2005 3:04 PM
>> >To: address@hidden
>> >Cc: address@hidden
>> >Subject: verifymsg and branches
>> >
>> >
>> >
>> >I understand how verifymsg can be used to check the text in a
>> >commit message. The problems is that I'd like to have 
>> >different checks for different branches, and there is no 
>> >"branch name" variable that I can see to pass into a script 
>> >called from verifymsg. 
>> >
>> >So I went to see how scripts such as cvs_acls and activitymail
>> >get their branch information. cvs_acls seems to parse each 
>> >directory's CVS/Entries file on the client, and activitymail 
>> >seems to get it from the stdin for commitinfo. But I can't 
>> >pass the %l variable (the name of the file containing the 
>> >commit message) to anything but verifymsg and editinfo, and I 
>> >can't pass the same stdin to verifymsg.
>> >
>> >Any suggestions?
>> >
>> >~Matt
>> >
>> >p.s. I suppose a two step process of checking the message and
>> >recording the results for all possible branches somewhere, and 
>> >then modifying cvs_acls to check for an acceptable message 
>> >once the branch is known might work. Bit hokey though.
>> >
>> >Environment: cvs server 1.12.9, older clients and SmartCVS 4.0
>> >
>> >
>> >_______________________________________________
>> >Info-cvs mailing list
>> >address@hidden
>> >
>> _______________________________________________
>> Info-cvs mailing list
>> address@hidden

reply via email to

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