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

RE: question about unix file permissions

From: Tim Alsop <Tim.Alsop_at_CyberSafe.Ltd.UK>
Date: 2004-07-06 08:55:16 CEST

I agree, so what process do we need to use so that this bug/enhancement
is taken care of ?


-----Original Message-----
From: Sven Mueller [mailto:sm@leogic.com]
Sent: 06 July 2004 00:06
To: Tim Alsop
Subject: Re: question about unix file permissions

Tim Alsop schrieb:

> Bryan,
> Sorry if my last post was not 100% clear. What I was suggesting is
> the following procedure should work (in my opinion) :
> $ svn co file.sh
> $ chmod u+x file.sh
> $ svn ci file.sh
> I believe the above should be made to work because a change to the
> properties of a file using chmod should be treated in the same way as
> edit to the file contents.

Well, at least the above case should be monitored.

svn add file.sh
svn ci file.sh
chmod +x file.sh
svn ci file.sh

shoule result in the same repository representation of file.sh as

chmod +x file.sh
svn add file.sh
svn ci file.sh

both should set the svn:executable property in the repository IMHO so
that in both cases a new checkout of file.sh results in a copy of
file.sh which is flagged executable (mode rwxr-xr-x probably).


---------------------[ Ciphire Signature ]----------------------
From: sm@leogic.com signed email body (672 characters)
Date: on 05 July 2004 at 23:05:50 GMT
To:   tim.alsop@cybersafe.ltd.uk
: The message above has been secured using Ciphire Mail.
: Verify this signature and download your free encryption
: software at www.ciphire.com. The three garbled lines
: below are the sender's verifiable encoded signature.
------------------[ End Ciphire Signed Message ]----------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Jul 6 08:58:03 2004

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

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