Michael Witten <mfwitten@xxxxxxxxx> writes: > On Sat, Oct 1, 2011 at 19:47, Andreas Krey <a.krey@xxxxxx> wrote: > > > The question is, should git forbid two filenames that consist > > of the *same* characters, only differently uni-encoded? I don't > > think anyone would make two files named 'Büro', with different > > unicode encodings. But as far as I know that is a shady area. > > So, let's leave git's current behavior as the default and provide > a config variable that when set, tells git to handle file names > in terms of characters rather than bytes. You meant here _graphemes_, not Unicode codepoint when talking about characters, didn't you? IIRC the problem with MacOS X is that it accepts different composition when creating a file from what it returns when asking for contents of directory (NFD if I remember correctly, which is less used). There are some beginnings of sanely handling filesystem encoding in Git (the framework), but it is currently underutilized only to handle case-sensitivity and case-preserving. -- Jakub Narębski -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html