Jack,
Correct me if I'm wrong, but that would assume the script somehow knew the
location of the workspace in which the commit is taking place. Since
anything that commitinfo kicks off is only passed the directory and file
name, I don't know how you could derive the workspace directory. Of course
my situation is complicated by the fact that the repository is on a Sun box,
while the developers performing the commits are on NT system. Any thoughts?
Thanks,
-Scott
-----Original Message-----
From: Jack Christensen [mailto:[EMAIL PROTECTED]]
Sent: Friday, March 31, 2000 12:54 PM
To: [EMAIL PROTECTED]
Subject: Re: Locking branches and/or trunk
I simply wrote a script which is run by 'commitinfo'. It examined the
CVS/Entries file to determine if all checked in files are on the correct
branch.
thanx,
jack c.
Scott Pyatt wrote:
>
> 1. Is there a way to lock a branch without affecting the other branches or
> the trunk?
>
> 2. Is there a way to lock the trunk without affecting the other branches?
>
> There does not appear to be an intuitive method for accomplishing this in
> CVS. It appears I can limit commits on a directory by directory basis
using
> commitinfo. However, there is no version or branch information passed to
> the associated programs that commitinfo launches.
>
> My environment consists of the CVS repository on a SPARC Solaris 7.0
system,
> with the developers using WinCVS on NT systems. Thanks in advance.
>
> -Scott Pyatt
