[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Suggestion: Property "svn:executable" result in set "Read & execute" permissions in Windows

From: Felix Saphir <felix.saphir_at_kantarmedia.com>
Date: Mon, 03 Jun 2013 21:12:57 +0200

Am 03.06.2013 19:18, schrieb Ben Fritz:
> On Mon, Jun 3, 2013 at 10:42 AM, Felix Saphir
> <felix.saphir_at_kantarmedia.com> wrote:
>> Am 03.06.2013 17:02, schrieb Ben Fritz:
>>>
>>> Actually, I think *NOT* having the feature encourages doing something
>>> you should not do.
>>>
>>> If Windows would set the executable bit, then users could use SVN only
>>> on Windows, and just use the files (without touching SVN commands) in
>>> Linux.
>>
>> So you would continue to do something you shouldn't do if the behaviour
>> of svn:executable was changed?
>
> At work the main reason I use svn commands outside of Windows, is to
> avoid needing to do any chmod commands. Because, except for on
> Windows, "svn update" will automatically set the executable bits as
> needed.

Very well, but what does that have to do with network shares? You do
know that samba maps attributes between Windows and Unix? Have a look at
this <http://oreilly.com/openbook/samba/book/figs/sam.0507.gif>.

> So if Windows also set this bit, I would use SVN commands outside of
> Windows a lot less frequently, if I did at all.

So you still would share your working copies between OS? Then this would
be a feature that encourages users to do something they shouldn't do.

I also strongly recommend against executable files on network shares.

Felix

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=3057043

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2013-06-03 21:13:15 CEST

This is an archived mail posted to the TortoiseSVN Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.