"Tim Alsop" <Tim.Alsop@CyberSafe.Ltd.UK> writes:
> I agree, so what process do we need to use so that this bug/enhancement
> is taken care of ?
Send a patch to the dev@subversion.tigris.org list. Or, if you
haven't time to produce a patch (which is fine, of course), then file
an enhancement issue about how Subversion could/should notice that
changes to executable status are a kind of local modification.
This doesn't guarantee it will get taken care of by any particular
date -- but regardless, it's the first step toward making it happen.
Best,
-Karl
> -----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
> 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.
>
> 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).
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Jul 6 18:53:13 2004