[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: creating policy
From: |
mthread |
Subject: |
Re: creating policy |
Date: |
Mon, 17 Sep 2007 05:29:36 -0000 |
User-agent: |
G2/1.0 |
On Sep 14, 6:52 pm, Todd Denniston <address@hidden>
wrote:
> mthread wrote, On 09/14/2007 07:22 AM:
>
>
>
> > Hi,
> > Thanx everyone for the help. Currently we have given only read
> > permission for the testing team. Although they cannot make any
> > modification in the repository, one thing that worried me is the
> > availability of CVS directories when they checkout a version. I would
> > like to know if the presence of CVS directory might cause any issues
> > in future(like being able to modify the repository in some way)
>
> Only if the _user_ with the CVS [sandbox status dir with Entries, Repository &
> Root files] directory has write access to the repository already, i.e., the
> status directory does not confer any access control, only provides sandbox
> state.
>
> --
> Todd Denniston
> Crane Division, Naval Surface Warfare Center (NSWC Crane)
> Harnessing the Power of Technology for the Warfighter
hi,
thanx for the information
regards,
mthread
- creating policy, mthread, 2007/09/11
- Re: creating policy, Jim Hyslop, 2007/09/12
- Message not available
- Re: creating policy, mthread, 2007/09/13
- Re: creating policy, Denniston, Todd A CIV NAVSURFWARCENDIV Crane, Code 6067, 2007/09/13
- Re: creating policy, Jim Hyslop, 2007/09/14
- Message not available
- Re: creating policy, mthread, 2007/09/14
- Re: creating policy, Todd Denniston, 2007/09/14
- Message not available
- Re: creating policy,
mthread <=