On Feb 27, 2006, at 02:40, Adam Mercer wrote:
>> svn propset svn:executable ON framelist.pl
>>
>> ...where "ON" can actually be any value at all, even,
>> counterintuitively, for example "OFF". To turn it off again, you
>> would need to use:
>>
>> svn propdel svn:executable framelist.pl
>
> Thanks that did it, but why did it work for the other scripts?
Looking back at the list of files you showed...
> [ram@zippy waveburst]$ ls -l
> total 48
> -rw-r--r-- 1 ram ram 157 Feb 26 19:38 config.ini
> -rw-r--r-- 1 ram ram 1846 Feb 26 19:38 framelist.pl
> -rwxr-xr-x 1 ram ram 216 Feb 26 19:38 generateDAG.pl
> -rwxr-xr-x 1 ram ram 183 Feb 26 19:38 generateIn.pl
> -rwxr-xr-x 1 ram ram 796 Feb 26 19:38 pre.pl
> -rwxr-xr-x 1 ram ram 3005 Feb 26 19:38 waveburst_break.py
I'm betting you did something like this:
$ svn propset svn:executable *.pl *.py
What you have to know is that your shell expands those asterisks
before Subversion ever sees the command. So what gets passed to
Subversion is actually this:
$ svn propset svn:executable framelist.pl generateDAG.pl
generateIn.pl pre.pl waveburst_break.py
In other words, Subversion sets the svn:executable property of the
files generateDAG.pl, generateIn.pl, pre.pl and waveburst_break.py to
"framelist.pl", which, just like any other value, is a valid value
for that property which turns on the executable bit.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Feb 27 03:14:14 2006