[Top][All Lists]

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

Re: Passing filename to verifymsg script

From: Mark D. Baushke
Subject: Re: Passing filename to verifymsg script
Date: Tue, 16 Aug 2005 08:43:31 -0700

Hash: SHA1

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
Version: GnuPG v1.2.3 (FreeBSD)


reply via email to

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