Re: Passing filename to verifymsg script

[Derek Price]

Or use the version of CVS in CVS.  I just added %{sV} to verifymsg, like
loginfo has %{sVv} (the full %{sVv} would be harder for verifymsg since
the new revision is not calculated yet).

Derek


Mark D. Baushke wrote:

> 12thMan <address@hidden> writes:
>
> >I am trying to implement separate verification logic for different
> >types of files.  For instance, I would like to require a bug number in
> >the comments for .java and .properties files, but not in the comments
> >for .doc files.  Assuming all of these files reside in the same
> >repository is there an easy way to do this?   Ideally I would like to
> >be able to pass the name of the file being modified to my verifymsg
> >script, but this doesn't seem to be possible.
>
> >Any suggestions would be much appreciated.
>
>
> There are a couple of ways to do what you want.
>
> One way would be to 'remember' the kind of testing you wish to do by
> writing appropriate information in your commitinfo trigger and then
> refer to it from your verifymsg trigger. This method should work for
> either client/server or local mode commits and is probably the more
> flexible of the approaches, but probably require the most work.
>
> Another way would be to use 'cvs -n status -l' each time the verifymsg
> is run in order to get a list of files in the current directory that are
> being committed. This works in client/server mode (either :ext: or
> :pserver:), but not in local mode.
>
> You may wish to examine how contrib/commit_prep and contirb/log_accum
> save/use information between triggers for ideas.
>
>     -- Mark


_______________________________________________
Info-cvs mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/info-cvs



-- 
Derek R. Price
CVS Solutions Architect
Ximbiot <http://ximbiot.com>
v: +1 717.579.6168
f: +1 717.234.3125
<mailto:address@hidden>