Re: [Gnu-arch-users] Re: centralized mail commit hook

[Mikhael Goikhman]

On 29 Mar 2005 22:52:24 +0200, Matthieu Moy wrote:
> 
> Cameron Patrick <address@hidden> writes:
> > Yes.  I use the attached script in combination with asuffield's
> > arch-trigger script
> 
> Exactly what I was looking for !

If you like it, you may also try a new composite command "axp triggers"
that implements a proper commit notification system with easy interface.
For every limit (version, branch, category or the whole archive) that you
want to watch, run "axp triggers add LIMIT" command. You will be asked to
confirm/tweak the trigger action that is just a regular custom script.
By default, the action is to send a mail to yourself, but you may supply
"--email". The already existing revisions are not triggered normally.

Place "axp triggers process --quiet" command to your crontab. That's all.
Some useful 'process' options are --skip, --test and --log-to FILE.
All failures should be gracefully handled with detailed description.

If you don't supply the custom script, the email sent for every new
revision contains an output similar to "tla changelog"; there is a
switch to send the plain revision log instead. The custom script has
access to 20 shell-escaped variables containing all kinds of revision
names and log fields (if one ever wants to change the sane defaults).

There are more subcommands, namely list/delete/move/edit, to manipulate
everything from the command line. You may want to read --help of every
subcommand, or the autogenerated online help at:

  http://migo.sixbit.org/software/axp/commands/triggers/

P.S. Thanks to those who mentioned "tla|baz abrowse --since" options,
such implementation improves the slow archive performance drastically.

Regards,
Mikhael.