[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: common vs confidential development parts
From: |
James Knowles |
Subject: |
Re: common vs confidential development parts |
Date: |
Sat, 22 Dec 2001 14:03:14 -0700 |
> I did try that solution (because that would be the simplest solution...)
> but when
> a user of group A performs a checkout or a commit, the whole cvs process stops
> with an error when encountering any file of group B. Is there a flag to
> activate to
> avoid such troubles (ignoring such permissions errors)?
I don't understand how this could happen. If group A can neither read nor
write group B files, how it is possible that a group A person can encounter
group B files? Please say developers are not sharing the same sandbox.
If anybody in group A does a checkout, how is it that they are attempting to
access group B files? It sounds like the CVS setup needs to be tweaked a
bit.
Just shooting in the dark here...
--
None are more hopelessly enslaved, as those who falsely believe they are
free.