[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-05 08:55:59 CEST


Sorry if my last post was not 100% clear. What I was suggesting is that
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 an
edit to the file contents.


-----Original Message-----
From: Bryan Donlan [mailto:bdonlan@gmail.com]
Sent: 05 July 2004 00:33
To: Tim Alsop
Cc: Eric Wilhelm; users@subversion.tigris.org
Subject: Re: question about unix file permissions

On Sat, 3 Jul 2004 08:25:45 +0100, Tim Alsop
<tim.alsop@cybersafe.ltd.uk> wrote:
> Eric,
> Thank you. This is good news.
> So, if the properties of a file are changed, surely this should be
> recognised as a change to the file and handled in the same was a
> modification to its content during the next commit ? Instead, it
> this is not the case and properties are only transferred into
> after initial add.
> I will try and use svn propset command to change my files, but I would
> prefer subversion to be more consistent so that future permission
> changes are recognised in the same was as content changes.
> Thanks, Tim.

What do you mean? Property changes can be committed in any revision -
but if you set a property to a value it's already set to it's not a
change. Note that unsetting svn:executable is done with 'svn propdel
svn:executable', not 'svn propset svn:executable 1' - the value of
svn:executable is replaces with *, only its presence matters.

For more information on properties, see

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Jul 5 08:58:21 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.