Hi,
On 10/24/13 22:05, Branko Čibej wrote:
As Thorsten has pointed out, this is a different case. BTW, I have a
similar solution, like contrib/asvn, but the current operation of svn
makes it impossible/very hard to make it work, because it screws up
real file permissions on each commits.
Yes, that's a valid point. Subversion will possibly write the file
and/or change permissions on commit in two cases, I think:
* The file has the svn:needs-lock property set, and has to be made
read-only after commit; or,
* The file contains keywords, which have to be updated (e.g., author
and revision change after a commit).
I'm not aware of these.
Subversion doesn't rewrite the file, because it has the same inode
before and after the commit. And according to a trace, it does a direct
chmod on it.
So if neither of these are standing, is this a bug?
