Sorry Ben,
I didn't reply to the list.
Ben Collins wrote:
> >
> > So, initially my thoughts were very simple -- what business is it of a
> > version control system to pay attention to file perms, which in my
> > opinion are more like OS metadata than file attributes?! However, I
> > have since yielded grounded over the execute bit, though I still am
> > not a proponent of even that.
> >
>
> IMO, if we keep the default behavior of leaving them alone, but allow a
> perm property to override (or mask) the users settings, that would be
> great.
>
Currently, is the execute bit set "automagically" from a working copy or
does it require a propset/propedit?
IMHO, it seems like the only way you could make everyone happy would be to
allow more than one set of permissions.
Then have the ability to specify which/if any to apply. This would come in
handy for deploying scripts and binaries.
I'm sure this could become quite sticky however.
I'm completely new to Subversion, but just having the ability to store my
own properties is great (I can do that right?).
I can easily see creating my own permission properties and having a delivery
script which uses those properties to deploy application files for
development vs production.
Glenn
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Mar 27 23:20:20 2002