My umask is 022 (and I've never changed it, not since my early uni days on those old SGI Indigos when I was paranoid). I'm wondering if somehow the file was originally created read-only (I can't think why that might be!?) and that CVS is remembering it?
Karl Fogels "Open Source Development with CVS" suggests that this might be the case and that the repository option PreservePermissions might have something to do with it. It looks like the solution (aside from me chmod'ing the files +w each time I make a change) is to either set the permissions in the repository itself, or to enable the PreservePermissions setting on the server side (although he hints at some other implications). --Wez. On 09/23/02, "Andi Gutmans" <[EMAIL PROTECTED]> wrote: > At 07:22 PM 9/23/2002 +0100, Wez Furlong wrote: > >Am I the only one who is getting their files chmod'ed to read-only > >every time I do a CVS commit? > >In particular, main/user_streams.c keeps doing this which is quite > >annoying - is there some setting on the server side that affects this? > >(and do we want it switched on?) > > No idea. It's never happened to me. Not that I think it can have anything > to do with it but is your umask OK? -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, visit: http://www.php.net/unsub.php
