Date: Mon, 29 Sep 1997 07:55:30 -0700 From: John Polstra <jdp@polstra.com> To: hackers@freebsd.org Subject: Re: CVS permissions after checkout Message-ID: <199709291455.HAA25802@austin.polstra.com> In-Reply-To: <19970929091641.ZL20420@uriah.heep.sax.de> References: <199709260008.TAA10113@bob.scl.ameslab.gov> <199709290427.VAA22383@austin.polstra.com> <19970929091641.ZL20420@uriah.heep.sax.de>
next in thread | previous in thread | raw e-mail | index | archive | help
In article <19970929091641.ZL20420@uriah.heep.sax.de>, J Wunsch <joerg_wunsch@uriah.heep.sax.de> wrote: > > Oh, no longer the missing group write permissions iff the file > creation missed them? That is great! That's right -- as long as you have a umask of 002 or something like that (00x) when you do your CVSup updates. Also, the server you are updating from has to have at least version 15.2 for this feature to work. It should have been that way all along. But I started out with the strange idea that if a user changed the permissions of some of his files, then CVSup should honor that and not change them back. Several people complained (nicely) about that, and I became convinced that they were right. Starting with the version 15.2, CVSup maintains this condition for each file: (client's modes & ~umask) == (server's modes & ~umask) where "umask" is that of the client. -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199709291455.HAA25802>