*been going over older posts that seemed interesting*
Interesting... when did this happen? I've used CVS for a while in order to
version the configuration of my UNIX systems, and was a semi-happy user of
it's ability to version file permissions. The code was very buggy (and
caused the client to crash a lot); enough so that they actually decided to
deprecate it and remove the feature at some point. I was therefor quite
interested in Subversion's claim that at some point it would fully support
UNIX file permissions.
If you go back to the Subversion design documents:
<quote src="http://www.tigris.org/files/documents/15/48/svn-design.txt">
* Clients use properties to store file attributes, as described
above. For example, the Unix Subversion client records the files'
permission bits as the value of a property called
`svn-posix-access-permission'. Operating systems which allow files
to have more than one name, like Windows 95, can use directory
entry property lists to record files' alternative names.
</quote>
Sincerely,
Jay Freeman (saurik)
saurik@saurik.com
----- Original Message -----
From: <cmpilato@collab.net>
To: "Tim Moloney" <moloney@mrsl.com>
Cc: <dev@subversion.tigris.org>
Sent: Wednesday, February 27, 2002 10:15 AM
Subject: Re: file permissions
> Tim Moloney <moloney@mrsl.com> writes:
>
> > When I check out files from subversion, they no longer have the correct
> > file permissions. I don't know if they are being lost during the commit
> > or the checkout.
>
> Versioning of permissions is a) not implemented yet, and b) planned
> *only* to cover the 'executable' bit.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Mar 26 23:52:25 2002