[cvsnt] Is it possible to lock a user out of HEAD, but grant them full access to a branch?
TBeavers at SkywaySoftware.com
Mon Oct 13 16:08:52 BST 2008
Fisheye is not broken, but I did incorrectly report what Fisheye reports
when adding new files to a BRANCH.
When a new file is added to a BRANCH, Fisheye sends two emails, one
reports version 1.1 of the new file was deleted from HEAD and the other
reports version 126.96.36.199 was added new on the BRANCH.
As for my ACL issue and not being able to write new files to a BRANCH
due to HEAD being locked down, I think it was caused by the order in
which I setup the ACL's initially.
I removed all ACL's and then reconfigured by locking down HEAD first,
then giving permissions to BRANCH and all works fine now.
I will most likely go back and reconfigure again using your
recommendation of ACLmode=normal, but didn't want to muck with the
majority of my current users at this time.
Thanks for your help!
From: Arthur Barrett [mailto:arthur.barrett at march-hare.com]
Sent: Thursday, October 09, 2008 4:47 AM
To: Terry Beavers; cvsnt at cvsnt.org
Subject: RE: [cvsnt] Is it possible to lock a user out of HEAD,but grant
them full access to a branch?
> Not only do we receive an email from Fisheye reporting the new file
> added on the branch, but we also receive an email that reports the new
> file has been added on HEAD as well, although the file doesn't
> physically reside on HEAD at that point, only the branch.
Sounds like Fisheye is broken - the e-mail integration included in CVSNT
doesn't have that problem.
> Lock down HEAD for READ only access
> cvs chacl -R -u tbeavers -a
You are probably better off using ACLmode=normal (in CVSROOT/config) so
that by default users do not have access so you do not need all the
Please try that and use the latest 2.5.04 RC for both clients and
If the problem still exists then we can look into it.
More information about the cvsnt