[cvsnt] Restriction top-level module creation

Tony Hoyle tony.hoyle at march-hare.com
Thu Feb 16 00:33:50 GMT 2006


Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.


Rahul Bhargava wrote:
> Being rude on a public mailing list is inappropriate.  Please be 
> constructive and stick
> to technical arguments if needed.

That isn't rude at all.  It's just responding to a completely incorrect 
reply.

> Here you don't want to set a default ACL on the root. That is the whole 
> point. If a user wants to
> control what modules can be added on a cvsroot ahead of time (prior to 
> import) how can that
> be done with whacl ? If you are going to suggest allow write access on 
> root, that is what the
> WANdisco based solution tried to avoid.

*of course* you want a default ACL on the root.  He wants to restrict 
the creation of new modules - there are two correct anwers - either set 
the ACLMode in the repository so the default is deny, or set an ACL in 
the root so that only administrators or specific users can write to it.

That's what the OP was after and didn't realize that he could do it. 
You decided to turn it into an advertising oppoortunity.

> Hello! what's wrong with telling CVSNT users about other options in a 
> very specific context.

Two thirds of your post were a blatant advert for a commercial product. 
  This is not allowed on this list.  You were *told* this the first time 
you did it.  You might have got away with a line or two, but you decided 
to make it the majority of your post.

Tony




More information about the cvsnt mailing list
Download the latest CVSNT, TortosieCVS, WinCVS etc. for Windows 8 etc.
@CVSNT on Twitter   CVSNT on Facebook