Google Summer of Code - Case Insensitive Filenames

[Austin English]

On Tue, Mar 25, 2008 at 9:08 AM, Kai Blin <kai.blin at gmail.com> wrote:
>  Ok, let's think about the use case here. My idea is that this is going to be
>  used on a new WINEPREFIX on a call to wineprefixcreate. We create a new
>  directory here and can make sure we're not doing anything stupid here. I'm
>  not suggesting to use this for the whole file system. If I have two files
>  with filenames that only differ in capitalization, this will only add
>  confusion.
>
>  That's why I still think having an option to delete unwanted files is useful.
>

An option yes, but it should not be the default course of action. As
Rahyen said, a predictable order should be used, and when there are
conflicts, pick the first in that order for presentation through the
FUSE system. User can then rename files/delete files to get the one
they want (or if possible, have a configuration menu to adjust chosen
file order/allow exceptions, etc.).