[Top][All Lists]

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

Re: branch access control

From: Mark D. Baushke
Subject: Re: branch access control
Date: Tue, 03 Sep 2002 10:44:38 -0700

Hi Douglas,

> From: Douglas Finkle <address@hidden>
> Date: Tue, 3 Sep 2002 13:06:15 -0400 
> 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. 

You are either mistaken or you are running a modified cvs that is not
based on the sources.

The URL: says:

|    Note: when CVS is accessing a remote repository, `commitinfo' will
| be run on the _remote_ (i.e., server) side, not the client side (*note
| Remote repositories::).

> I've yet to see a good reason why a patch that passes the
> branch tag can't be incorporated into, for example, commit.c
> so the rules can be implemented completely on the server side.

Putting a 'cvs -Qn status filename' into a commitinfo log loginfo script
WILL run on the server side. It works today with versions of cvs going
back at least as far as 1.10.5 (the oldest version I had on hand to test
with for compatibility just now).

> Maybe there's more to it than I'm seeing?

It seems likely this is true.

        -- Mark

reply via email to

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