Re: [DESIGN] svn:resolve-case

Joshua Varner wrote:

>By this argument, the best place to enforce end-of-line conventions is on
>the server as well. The properties do not fix the problem, just like the
>eol properties do not fix that problem. The client changes its behavior in
>the presence of this property. The actual detection and resolution of eol
>and case issues should be in the client software.
>
>
You've not been listening.

Eol-conversion is a convenience. Case-change detection is not, it's a
way to avoid problems we currently have on case-insensitive file systems.

Your proposal talks about imposing a file naming policy. What I said is
that this won't fix problems that arise from faulty detection of
case-conflicts in the working copy.

Simply put, your proposal wouldn't fix the problem, it would just make
one cause of the problem less likely to happen. And judging by the
various reports I've seen, it's not the most important cause.

>The other issue that is brought up frequently with a server side hook, is
>that you would have to exhaustively search all of the locales
>
Not at all, for what you're proposing. When you define a file naming
policy, you can easily limit the set of characters allowed in a file name.

-- Brane

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Aug 23 03:49:55 2005