On Mon, 21 Jan 2008, Peter Karlsson wrote: > > It is relevant because the Mac OS file system stores file names as a > sequence of Unicode code points, in a (apparently slightly modified) > normalized form, whereas Git prefers to see file systems that store > file names as a sequence of octets, which may, or may not, actually map > to something that the user would call characters. No. The *only* issue is that git doesn't normalize. You can think of git as a UTF-8 namespace all you want, and it will work together wonderfully with OS X. Git just doesn't force-normalize the names. > You apparently prefer the text-as-sequence-of-octets, which I tend to > dislike because I would have thought computer engineers would have > evolved beyond this when we left the 1900s. Some of us just know what we're doing, and have been working with UTF-8 for a long time. It's not about sequence-of-octets, it's about not corrupting the data. You think data should be changed behind peoples backs, potentially causing corruption due to unintended conversions. And I don't. You can call me "left behind in the 1900s", but that's apparently because you don't understand the issues. Data corruption wasn't something that magically became ok just because we switched into a new century. Linus - 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
