[Top][All Lists]

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

RE: branch access control

From: Frederic Brehm
Subject: RE: branch access control
Date: Tue, 03 Sep 2002 13:45:35 -0400

At 01:33 PM 9/3/2002, Douglas Finkle wrote:
> At 01:06 PM 9/3/2002, Douglas Finkle wrote:
> >Yes, you're right... you can use either of the two methods
> >mentioned, 'cvs status', or the Entries file.  Still, both
> >of these methods are client side and their success depends
> >upon software (e.g. Perl) that may or may not be present on
> >client machines.
> The script named in commitinfo executes on the server side.

Sure, but what about the data that the script looks at?  On the
server side of things there is no CVS/Entries file, and 'cvs status'
will fail if there's no checked out sources.

Somebody said:
> The commitinfo script is running in a directory where the
> files given on
> the command line reside as local files. There is also a copy
> of the CVS
> directory present and the CVS/Entries file contains the
> branch information
> if you want to parse it. There are two ways you could get
> that information.

I believe that is a true statement for both client/server and local modes.

Frederic W. Brehm, Sarnoff Corporation,

reply via email to

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