2010 10:33
> An: Matthias Weyh
> Cc: users@subversion.apache.org
> Betreff: Re: AW: merging executable binaries
>
> Matthias Weyh wrote on Wed, 7 Jul 2010 at 09:15 -:
>> Hello,
>>
>> I have added a command list for reproducing the issue.
>>
>
> T
already included in one of the later subversion releases?
Thanks,
Matthias
-Ursprüngliche Nachricht-
Von: Daniel Shahaf [mailto:d...@daniel.shahaf.name]
Gesendet: Donnerstag, 8. Juli 2010 10:33
An: Matthias Weyh
Cc: users@subversion.apache.org
Betreff: Re: AW: merging executable binaries
but
> this will change with the commit"
> Sending.
> Sendingexecutable.bin
> Transmitting file data .
> Committed revision 5.
>
> $ ls -la
> total 16
> drwxr-xr-x 3 devtsd devtsd 4096 2010-07-07 08:07 .
> drwxr-xr-x 12 devtsd devtsd 4096 2010-0
7-07 08:07 .svn
-Ursprüngliche Nachricht-
Von: Daniel Shahaf [mailto:d...@daniel.shahaf.name]
Gesendet: Dienstag, 6. Juli 2010 20:35
An: Matthias Weyh
Cc: users@subversion.apache.org
Betreff: Re: merging executable binaries
It's not clear to me exactly what you did. (The most unamb
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
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
