Justin Erenkrantz <jerenkrantz@apache.org> writes:
> On Thu, Aug 22, 2002 at 12:41:12AM -0700, Bill Tutt wrote:
> > Commentary on entire proposal:
> > Trying to mesh Subversion ACL behavior into OS specific and indeed WC
> > specific visible behavior just seems wrong. Subversion's ACL system
> > should be about securing SCM operations not defining the assigned ACEs
> > of the generated files in the working copy.
>
> My question back to you is why shouldn't it? If I can't modify
> the file on the repository, why should I (by default) be able to
> modify the file locally?
I'm probably missing something obvious here, or have my head on
sideways, but how does one reconcile ACL stuffs between the repository
and the current OS of the client in light of the fact that someone's
login/username on the computer might be completely different than the
name used for committed to the repository?
I mean, generally speaking, are we talking about Subversion attemping
to use the OS to mirror permission sets described to the client by the
repository?
Be gentle. (:-]
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Aug 22 19:10:37 2002