Re: svn commit: rev 7963 - trunk/subversion/libsvn_wc

Philip Martin <philip@codematters.co.uk> writes:

> This means that Subversion will now add group/world read access
> even when the umask of the process removes it, Subversion is no
> longer respecting the process umask. Now the group/world read
> access is not really a problem since the file is empty, but
> ignoring the umask is wrong in principle.

I was going for the minimal impact to address my problem.
Really, i don't think we should have empty-file to begin with.
On UNIX we have /dev/null and on Windows they have NUL or
whatever.

Subversion is really an inode hog, and i'm not sure what all it
buys us. A README in every admin dir? Give me a break. Lots of
that stuff could be shared by putting it only in the top level of
the wc (like empty-file, if we really do need it).

> It would be better to create the file using the default
> permissions and then use the set read-only function to remove
> write access.

Add a whole 'nother system call? For what? Why on earth do we
think this file has to be read-only? I can imagine some
responses (though not necessarily from you), and they are not
impressive.

--
Eric Gillespie <*> epg@pretzelnet.org

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Dec 9 01:58:43 2003