[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Unversioned files with invalid UTF-8 sequence in name confuse svn

From: Branko Čibej <brane_at_apache.org>
Date: Tue, 1 Mar 2016 17:12:05 +0100

On 01.03.2016 16:58, Markus Schaber wrote:
> Hi, Bert,
>
> From: Bert Huijben [mailto:bert_at_qqmail.nl]
>> From: Markus Schaber [mailto:m.schaber_at_codesys.com]
>>> Hi, Brane and Vincent,
>>>
>>> From: Branko Čibej [mailto:brane_at_apache.org]
>>>>> However Subversion doesn't handle that (BTW it would be much
>>>>> better to
>>>>> remember the expected locale by storing it in the .svn directory
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
>>>>> rather than giving obscure error messages: if it did, Subversion
>>>>> would know that the user was using an incorrect locale without any
>>>>> ambiguity).
>>>> And if the user changes the locale for valid reasons, the Subversion
>>>> working copy would break in a different way.
>>> I guess we would need some "change locale" operation, which would at
>>> least update the saved locale in the .svn directory.
>> There is no saved locale in the .svn directory...
> Currently, yes, but it was suggested in the discussion, see the line above.

The major problem with the "saved locale" idea is that it creates yet
another potential discrepancy. I really can't imagine how we'd be doing
the majority of our users a service by adding another knob that can
seriously break things when it's misconfigured, but doesn't do anything
useful most of the time.

-- Brane
Received on 2016-03-01 17:12:11 CET

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.