[Top][All Lists]

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

RE: verifymsg script

From: Christopher.Fouts
Subject: RE: verifymsg script
Date: Wed, 23 Mar 2005 10:43:06 -0500

>-----Original Message-----
>From: Jim.Hyslop [mailto:address@hidden 
>Sent: Wednesday, March 23, 2005 10:05 AM
>To: Fouts Christopher (IFNA MP DC); address@hidden
>Subject: RE: verifymsg script
>address@hidden wrote:
>> I finally tried this, and the script just echoes
>> out the lines in my rcstemplate file that do not
>> begin with "CVS". So how can I modify my rcstemplate
>> file to contain the branch tag? Adding the $Name$
>> keyword did NOT do it of course.
>Well, it's a bit ugly, but here's a possibility:
>verifymsg runs in the local directory, or (I think - I haven't 
>checked this
>part) in a copy of the workspace if you're doing 
>client/server. This means the CVS/Entries file is available. 
>You could add something like this to your verifymsg scripts:
>cut -d/ -f2,6 CVS/Entries | grep -E '/T' | sed 's@/T@, CVS tag: @' >>$1
>This pulls all the lines from CVS/Entries that have a tag 
>associated with the file, and appends them to the checkin 
>message in the form "[filename], CVS tag: [tag]" You can 
>rework this to append "(none)" if there is no tag. You'll also 
>have to add code to recurse into subdirectories.
>Make sure the RereadLogAfterVerify option in CVSROOT/config is 
>not disabled.
>One drawbacks is, you have no way of knowing which files the 
>message applies to, so you'll have to write all the tags to 
>the log message. For example, if your directory tree contains 
>100 files, and you check in only one file, the log message 
>will have 100 file names mentioned in it.
>Jim Hyslop
>Senior Software Designer
>Leitch Technology International Inc. ( ) 
>Columnist, C/C++ Users Journal ( )

Ik I'll try this approach, but not necessarily the code since my
scripts are in PERL.



reply via email to

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