Use sticky bits on the group for your files. That way you keep the original author of the commit and can manipulate with group lists. But why you need permissions for your own sandbox?
-Nils Jakobson SWHTechnology ----- Original Message ----- From: "raptor" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]>; "Chris Barker" <[EMAIL PROTECTED]> Sent: Friday, September 28, 2001 10:28 AM Subject: Re: Right Permissons !? > What I've done was to set 'cvs' as a primary group for all the developers.. > and to give 'cvs' group write access to the whole repository.... Don't know > is this is the right way but it seems to work...!! > It was very annoing for me too..?? > One other thing I'm wondering is there a way to set automaticaly in same way > different pemissions when the files go to the working copy (during update) > !!! Anyone to have idea !? > > HtH > ===== > iVAN > [EMAIL PROTECTED] > ===== > > > _______________________________________________ > Info-cvs mailing list > [EMAIL PROTECTED] > http://mail.gnu.org/mailman/listinfo/info-cvs > _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
