RE: svn commit: r1452780 -

 /subversion/trunk/subversion/libsvn_subr/subst.c
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

We never change permissions on Windows. The functions in apr are no-op
stubs as you can't keep a acl chain in a chmod int.

We expect the permissions to be (properly) inherited from the parent
directory.

Bert From: Branko =C4=8Cibej
Sent: =E2=80=8E11/=E2=80=8E05/=E2=80=8E2013 13:51
To: dev_at_subversion.apache.org
Subject: Re: svn commit: r1452780
- /subversion/trunk/subversion/libsvn_subr/subst.c
On 11.05.2013 13:31, Stefan Sperling wrote:
> DST_TMP has more restrictive permissions than that. It is created with
> the mkstemp() function under the hood. So we can assume that the perms
> of DST_TMP are configured such that only the user running svn can
> access the file. So we always start off with something like 600 on
> DST_TMP. And we need to preserve the permission bits of the existing
> DST (whatever they are) when renaming DST_TMP on top of it.=20

So, on Unix, you chmod DST_TMP to DST's permissions before renaming. I
don't remember offhand what you do on Windows.

-- Brane

--=20
Branko =C4=8Cibej
Director of Subversion | WANdisco | www.wandisco.com
Received on 2013-05-11 15:02:46 CEST