It's not clear to me exactly what you did. (The most unambiguous way to explain yourself is to post a list of commands, starting from 'svnadmin create'.) However, if you run 'svn merge' and at the end of the operation a file has svn:executable set, then its +x permission should be set --- and if not, that's a bug.
Matthias Weyh wrote on Mon, 5 Jul 2010 at 15:54 -0000: > Hello, > > I have seen the following behaviour. > > added binary file to SVN with property svn:executable > executable bits are then set on the file > checked in the file > added a branch which included the file > modified the file in TRUNK > merged the change to branch > the executable flag on the file is then gone > however when I commit the merge the executable flag of the file is again > being set > > Is this the correct behaviour (is the executable flag supposed to be > missing after a merge - and then added when the file is actually > committed)? > > The behaviour is different for non binary executables (the executable > bits are always set in this case). > > The SVN version I used was 1.6.6 on Ubuntu 10.0.4. The filesystem on > which the working copy resides is EXT4. > > I hope someone can clear this up for me. > > Thanks, > Matthias > > >
