But can you handle the situation where different sets of files have
different valid PR's? I've been trying to figure a way round that for
ages...
Andy
-Original Message-
From: Chris Cameron [mailto:[EMAIL PROTECTED]]
Subject: RE: Triggers links to defect tracking systems
We use
Mark D. Baushke wrote:
...snip...
What I was thinking of doing was using the loginfo hook to
check the checkin comment to see that there is a PR number,
and then verify that this is a valid PR with checkin approval
(we've been having problems with some people checking in stuff
without
: RE: Triggers links to defect tracking systems
From: Tracy Brown [mailto:[EMAIL PROTECTED]]
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
From: Tracy Brown [mailto:[EMAIL PROTECTED]]
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
Tracy Brown writes:
Not only that, I have had problems issuing the export command
on my modules when templates are enabled with rcsinfo.
That should be fixed in CVS 1.11.1 (but don't use that release, use
1.11.1p1 instead).
-Larry Jones
Whatever it is, it's driving me crazy! -- Calvin
Sent: Friday, 11 May 2001 8:29 a.m.
To: 'Tracy Brown'; [EMAIL PROTECTED]
Subject: RE: Triggers links to defect tracking systems
From: Tracy Brown [mailto:[EMAIL PROTECTED]]
Sent: Thursday, May 10, 2001 11:33 AM
Mark D. Baushke wrote:
While this is possible if you are
using a local
repository
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Triggers links to defect tracking systems
Message-ID: [EMAIL PROTECTED]
Date: Mon, 02 Apr 2001 23:47:41 -
Hi,
Is there any facility in CVS to add hooks for customized actions?
For instance, requiring a Bug Number when you
Mark D. Baushke wrote:
Hi,
Is there any facility in CVS to add hooks for customized actions?
For instance, requiring a Bug Number when you check in a file,
verifying that bugnum against your defect tracking system, etc.
It is possible to do some integration of Bug Number and a
Hi David,
David wrote:
What I was thinking of doing was using the loginfo hook to
check the checkin comment to see that there is a PR number,
and then verify that this is a valid PR with checkin approval
(we've been having problems with some people checking in stuff
without permission, and I'd
