Re: [PATCH] check name svn special properties

Dear John,

>> Would it be more acceptable with a client-side configuration, which could
>> be update as necessary~? Something like :
>
> I'm even less happy with this than with a hard-coded solution, since at least
> with the latter, the universe of variants is limited. Anything that a user
> can edit can get even more wrongly configured (e.g. they mispell what is in
> their config file).

This argument is most curious! It applies to any configuration file on any
computer running any system that can indeed be messed-up in any way by any
user or admin.

AFAIK, the usual approach is to have the file installed with predefined
values, and editing such a config file should be a most rare event.

Well, I was most happy with the static stuff and the '--force' option,
but as you seemed to rejected it, so I provided another solution;-)

> If we want to "spell check" things like this, it is going to be based on the
> server's capabilities, even if the checking should happen in the client.

ISTM that if the server is to provide the client with some configuration,
it would be in the form of a server-customized version of the current
client configuration file? That would be the most straightforward
implementation. Then the ability to configure the client with a list of
allowed svn properties would be needed there also.

> Until such time as we can communicated server-resident configuration
> information to all of the clients, I think this is just a limitation we will
> have to live with.

Indeed, as the patch seems to be rejected, I have to live with this "feature".

Have a nice day,

-- 
Fabien.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org