[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: CVS access control
From: |
Tobias Brox |
Subject: |
Re: CVS access control |
Date: |
Wed, 26 Sep 2001 11:47:45 +0400 |
User-agent: |
Mutt/1.0.1i |
[Matthew Versluys - Tue at 10:45:53PM -0700]
> A typical file could look like this:
> READ ^Readable
> WRITE ^Writable
> READ ^Read/Access/But/Not/Below/Here$
> WRITE ^Write/Access/But/Not/Below/Here$
I'd say you should expand the syntax a bit:
READ ^public
WRITE ^development
DENY READ ^public/except/for/this/file$
When you're at it, you should also allow for different ruling on different
branches, not only directories.
I've been into the need for having write-permission (and it's a nice idea in
general) only to the a particular "sandbox" branch of a project.
That would be a nice feature in CVS, also because it _can't_ be supported
only on the basis of file permissions.
- CVS access control, Matthew Versluys, 2001/09/26
- Re: CVS access control,
Tobias Brox <=
- Re: CVS access control, yap_noel, 2001/09/26
- Re: CVS access control, yap_noel, 2001/09/26
- Re: CVS access control, yap_noel, 2001/09/26
- Re: CVS access control, yap_noel, 2001/09/26
- Re: CVS access control, yap_noel, 2001/09/26