RE: How to restrict access to branches

[Teala Spitzbarth]

This topic is a frequently discussed one on the alias.

There have been examples of commitinfo scripts posted on the alias
which enable you to restrict access to branches.  The one I use
is based on lock-branch.sh posted by Shubhabrata Sengupta, see:

http://mail.gnu.org/pipermail/info-cvs/2001-May/015311.html

I've recently discovered that my version of this script is not
handling recursive commits correctly.  I'm not sure yet whether
I introduced the bug or if it was present in the original script.
When I figure it out, I will repost an updated version of the
script if appropriate. 

Note: this script accesses the Entries file directly, 
it has already pointed out that it should be upgraded to use the
cvs status command to be independent of Entries file format changes
in the future.

Thanks,
Teala


-----Original Message-----
From: Datla, Raghav [mailto:address@hidden
Sent: Tuesday, January 08, 2002 10:29 AM
To: 'address@hidden'
Subject: How to restrict access to branches


Hi,
   Is there anyway to restrict the developers to access (I mean they
should
not able to make any modifications) the branch which was created
something
like PROD for production code.

Thanks inadvance,
-Raghav

_______________________________________________
Info-cvs mailing list
address@hidden
http://mail.gnu.org/mailman/listinfo/info-cvs