2008/9/17 Hendrik Maryns <qwizv9b02_at_sneakemail.com>:
> Mark Phippard schreef:
>> On Wed, Sep 17, 2008 at 5:11 AM, Hendrik Maryns
>> <qwizv9b02_at_sneakemail.com> wrote:
>>
>>> I am bothered by a problem I have been having for a while now. I have
>>> some TeX projects containing .tex, .pdf and other image files. They
>>> have been checked in with Subclipse from a Linux desktop. Somehow, the
>>> files are now marked as executable, since when I check them out on
>>> another Linux, they are. They are not in the original project, however.
>>> I have no idea how this change cam into being and cannot really
>>> reproduce it, since e.g. my latest project doesn't suffer from this.
>>> Anyway, I'd like to make the files in the projects that have this
>>> problem non-executable again. Changing the permissions does not give
>>> any change in the Synchronizing perspective. Is there a way to get this
>>> done? If not in Subclipse, then maybe from the command line?
>>
>> Look at the SVN Properties on one of these items and see if the
>> svn:executable property it set. If it is, then SVN will set the
>> executable property on the file.
>
> Some of them had svn:executable set to *, indeed. But how could this
> be, since I have never set it myself explicitly? Others have the
> property svn:special, could this have the same effect?
>
See
http://svnbook.red-bean.com/en/1.5/svn.advanced.props.html#svn.advanced.props.auto
"Subversion will automatically set the svn:executable property on newly
added or imported files whose execute bit is enabled."
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subclipse.tigris.org
For additional commands, e-mail: users-help_at_subclipse.tigris.org
Received on 2008-09-17 13:56:35 CEST