Ryan Schmidt wrote on Sun, Jul 17, 2011 at 15:35:20 -0500:
>
> On Jul 16, 2011, at 15:14, David Myers wrote:
>
> > From what I have read in various places I thing I understand that...
> > subversion reflects the unix style permissions on it's subdirectories, in
> > the subversion directory tree.
> > If I want to make a specific location 'read only' I need to do this from a
> > new directory, and then files in this directory will acquire the
> > permissions of the parent directory.
> > subversion doesn't store the file permissions of a file directly it stores
> > it within the svn:properties
>
> Where did you read this? I don't think any of that is true. Subversion
> does not store permissions. There is no such thing as
> "svn:properties". The only permission Subversion can store is a file's
> execute bit; set the "svn:executable" property to an asterisk ("*") to
(any value will do; "*" is fine as long as one remembers to shell-quote it)
> indicate the file should have the execute bit, or delete that property
> to indicate it should not.
>
Also, svn:needs-lock files will be checked out as read-only until
they're "svn lock"ed. But we don't store permissions beyond that.
(There are wrapper scripts that do so, but Subversion itself doesn't.)
>
