On Dec 6, 2007, at 01:36, Mark Reibert wrote:
> On Thu, 2007-12-06 at 14:57 +0800, jianyun zhu wrote:
>
>> Hi guys, I am working for a team that uses Subversion for version
>> control, and I meet an confusing issue. Here's the scenario:
>>
>> I had a perl script named send_mail_daemon.pl, the file permission is
>> 777
>> -rwxrwxrwx 1 seth users 4662 Dec 6 14:23 send_mail_daemon.pl
>>
>> then someone changed it and I update
>>> svn update send_mail_deamon.pl
>>
>> after that, I found the file permission is CHANGED, which is not what
>> I want !
>> -rwxr--r-- 1 seth users 4662 Dec 6 14:25 send_mail_daemon.pl
>>
>> In fact, this changed file permission is an error in my project
>> because some one else cann't execute this script.
>>
>> could someone please tell me why things go like this? and, any
>> solution or advice would be appreciate
>
> Two questions:
>
> 1. What is your umask?
> 2. Is svn:executable set on this file?
To explain further: Subversion does not store any file's permissions.
All there is is the svn:executable property. If you set this on a
file, then Subversion will set the executable bit on the file when
you check it out. Otherwise, it won't.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Dec 6 09:05:45 2007