On Thu, 2007-12-06 at 13:19 +0100, Erik Huelsmann wrote:
> On 12/6/07, Vincent Lefevre <vincent+svn@vinc17.org> wrote:
> > On 2007-12-06 02:05:11 -0600, Ryan Schmidt wrote:
> > > To explain further: Subversion does not store any file's permissions.
> > > All there is is the svn:executable property. If you set this on a file,
> > > then Subversion will set the executable bit on the file when you check it
> > > out. Otherwise, it won't.
> >
> > But IMHO, if the svn:executable property has not changed and if the
> > x bit of the owner is correct, it would better it Subversion didn't
> > change the permissions.
> >
> > Note that setting the umask is not always possible as several files
> > may have different permissions.
>
> Subversion doesn't change permissions. It replaces the file which was there.
Subversion atomically replaces an existing file by writing a temporary
and calling rename(2). Thus the updated file will have the permissions
of the temporary, not the file to be updated. The rwxr--r-- permissions
could result, then, from the combination of svn:executable and an
atypical umask of 033. (Hence my earlier question about these two
values.)
--
----------------------
Mark S. Reibert, Ph.D.
svn@reibert.com
----------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Dec 7 08:22:35 2007