[Top][All Lists]

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

Re: permissions on branch

From: Shubhabrata Sengupta
Subject: Re: permissions on branch
Date: Tue, 15 May 2001 17:08:25 +0530

You can do that by writing a script which parses the CVS/Entries file for the branch info and then restrict the checkin if the branch falls in your restricted list.
You would need to plug this script into the commitinfo file, since the name of the file to be checked in would be passed to this script which you would use to parse the CVS/Entries for the branch info.
You might also like to put this script into some subdirectory of the CVSROOT directory and put an entry in the checkoutlist file so that a copy of the script is always checked out as soon as you checkin any changes to this script.
I can send you a sample script if you need one.
-----Original Message-----
From: Nils Jakobson <address@hidden>
To: address@hidden <address@hidden>
Date: Tuesday, May 15, 2001 4:58 PM
Subject: permissions on branch

Hello, maybe this already has been discussed and there is solution.
What I'm looking for is how to set permissions on specific branch names,
i mean, make some branches read-only. This is necessery because
it happens that wincvs users perform commits where they should not.
I believe this can be scripted in the CVS, but how and from where to
invoke it? It could be great to have config file with list of branch_names
to be treated as read-only.
Its more the development organization problem, but still.
-Nils Jakobson
SWH Technology

reply via email to

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