On Wed, 2004-10-13 at 00:19, Greg Hudson wrote:
> On Wed, 2004-10-13 at 00:23, Brian W. Fitzpatrick wrote:
> > > Ah, this came up on IRC. I don't think this is appropriate for a user
> > > pref. Really, for a given file (or project, in most cases, but policy
> > > might vary from place to place), all the users should agree on whether
> > > they're using locking messages or not. So a user pref has the wrong
> > > granularity; it applies to all files for a particular user, when we
> > > want
> > > the pref to apply to all users of a particular file.
> >
> > And the ability to have a server-side configuration rears its ugly head
> > again.
>
> A per-file property will do the job just fine now. We don't need global
> server-side configuration for this. We don't need global server-side
> configuration for anything, in my opinion; everything which has been
> proposed for global server-side configuration is something which users
> might want to vary per subtree or per file.
But you're assuming that the repository administrator wants this to be a
user preference. I'm talking about enforcing a particular policy.
-Fitz
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Oct 13 18:22:40 2004