On 10/30/13 09:56, Stefan Sperling wrote:
I believe it's the stupid code replaced below, which I wrote in r880420.
Because of it we end up setting perms based on umask upon every commit,
and end up expanding restrictive file permissions.
This patch should fix the problem.
Indeed, the file remains at 600 after commit. Can I expect it in the
next release?
Note that Subversion users cannot and couldn't ever rely on per-file
permission flags to keep files in a working copy hidden from other
users. This is because Subversion often resets permission bits when
it re-creates working files from temporary files. There is no way to
set bits of those files to something other than the current umask.
If the original file is there, subversion could copy its permissions.
Of course, if it's lost, it can't do it.
Thanks,
