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

Re: Let's discuss about unicode compositions for filenames!

From: Hiroaki Nakamura <hnakamur_at_gmail.com>
Date: Sun, 12 Feb 2012 00:35:39 +0900

2012/2/11 Branko ─îibej <brane_at_apache.org>:
> On 11.02.2012 13:05, Hiroaki Nakamura wrote:
>> 2012/2/9 Markus Schaber <m.schaber_at_3s-software.com>:
>>> Von: Stefan Sperling [mailto:stsp_at_elego.de]
>>> On Thu, Feb 09, 2012 at 12:20:14AM +0900, Hiroaki Nakamura wrote:
>>>>> [Upgrade options / backwards compatibility for proposed unicode normalization fix]
>>>> - Need to re-checkout existing working copies of the repository?
>>>>   => Yes, but only if config is changed from the default.
>>> Maybe this could even be avoided if newer clients (or an utility script) can "upgrade" the working copy to the normalized format.
>> Yes, if the working copy does not have filename collisions. However,
>> for compatibility,
>> we cannot let newer clients upgrade working copies automatically
>> because existing
>> working copies may have filename collisions.
> That's not entirely true, since we can detect the collisions in advance,
> and a partially upgraded working copy would still work
> From a practical point of view, it's very, very unlikely that there
> would be any such collisions in a valid working copy. People would tend
> to notice. :)

Yes, I agree wholeheartedly!
At work, I notice there are a few repositories which have NFC filenames
and NFD filenames. However there is no repository which have collisions
as far as I know.

)Hiroaki Nakamura) hnakamur_at_gmail.com
Received on 2012-02-11 16:36:14 CET

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