"Max Bowsher" <maxb@ukf.net> writes:
> Change:
>
> Make the contents of svn:keyworks fully case-insensitive.
>
>
> Objection raised by John Peacock (paraphrased):
>
> Keywords are case-sensistive in the working file, they should be so in
> svn:keywords too. We can't case-sensitivize the ones that are
> insensitive now, for compatibility, but don't spread the problem, and
> let's make them all case-sensitive when we reach 2.0.
>
>
> My response:
>
> I agree full case-sensitivity would be nicer. But, I think making
> svn:keywords fully case-insensitive now is a step towards consistency,
> and doesn't in any way prohibit stricter canonicalization when we
> reach 2.0.
Thanks, Max -- that was a tremendous help.
So, I think I agree with John. The best solution is simply to stop
documenting the case-insensitive versions, and mention *only* the
exact case-match versions.
But actually enforcing this when we reach 2.0 would annoy a lot of
people. IMHO we should only enforce it if upgrading to 2.0 requires
some sort of dump/load or other one-time repository conversion step
anyway. In that case, we could automatically fix the svn:keywords
property values as part of that conversion.
(Now that I look, I think we don't document the case-insensitive
versions anywhere, by the way.)
-Karl
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Feb 8 01:33:42 2005