RE: "Triggers" & links to defect tracking systems

[Chris Cameron]

We use a commitinfo script to check for commit permission, a verifymsg
script to validate the PR number and the loginfo file for putting the log
message into our fault database.  All this is done using pserver.
commitinfo and verifymsg are run before the commit occurs and loginfo
afterwards.

***************************************************************
Chris Cameron                       Open Telecommunications Ltd
Product Manager                           IN Product Management
address@hidden                           P.O.Box 10-388
      +64 4 495 8403 (DDI)                          The Terrace
fax:  +64 4 495 8419                                 Wellington
cell: +64 21 650 680                                New Zealand
Life, don't talk to me about life ....(Marvin - HHGTTG)


-----Original Message-----
From: address@hidden [mailto:address@hidden Behalf Of
Jerry Nairn
Sent: Friday, 11 May 2001 8:29 a.m.
To: 'Tracy Brown'; address@hidden
Subject: RE: "Triggers" & links to defect tracking systems



>From: Tracy Brown [mailto:address@hidden
>Sent: Thursday, May 10, 2001 11:33 AM
>> "Mark D. Baushke" wrote:
>>While this is possible if you are
>> using a local
>> > repository or the rsh/ssh transport, I don't know of any
>> way to do it
>> > with the :pserver: method of interaction.

>The rcsinfo file template generation hook works great with :peserver:

I haven't used this, but the documentation says that in client/server
operation, the template is copied from the server at the time of checkout.
Updates to the template on the server will not be reflected on the client
until a new checkout is done.
Jerry

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