On Tuesday, May 09, 2000 12:46 PM, Wade Stebbings [SMTP:[EMAIL PROTECTED]]
wrote:
> Thank you! I swore I saw this done before with stock CVS in a
> previous life.
>
> By inspection of your perl code, it tells me the CVS/Entries file
> gets copied to the temporary directory on the server side for
Thank you! I swore I saw this done before with stock CVS in a
previous life.
By inspection of your perl code, it tells me the CVS/Entries file
gets copied to the temporary directory on the server side for a
given request, and subsequently available for the commitinfo script
to read. This is exa
Marc Poinot wrote:
> Commit info is not really useful for control ! I would expect it
> was the one to use ! Did I missed something ?
Attached is a script that I wrote on my own time that we (occasionally)
use to protect the trunk/mainline from unauthorized access.
If you have a valid perl insta
Hi,
I'm currently developping a set of (Python) scripts
for at least this purpose:
- Check on the server side if the client is allowed
to commit on a given branch.
Our developpers have private branches and they can commit
whenever they want. But more "official" branches are controlled.
So
