2012/2/11 Branko Čibej <br...@apache.org>: > On 11.02.2012 13:05, Hiroaki Nakamura wrote: >> 2012/2/9 Markus Schaber <m.scha...@3s-software.com>: >>> Von: Stefan Sperling [mailto:s...@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) hnaka...@gmail.com
