On Thu, 11 Dec 2008, rdkrsr wrote: > > I'm sorry that I didn't answer to git mailing list address. So here > comes the email again. You have a broken filesystem. > $ git status > # On branch master > # Changed but not updated: > # (use "git add <file>..." to update what will be committed) > # > # modified: Documentation/IO-mapping.txt > # modified: include/linux/netfilter/xt_CONNMARK.h > # modified: include/linux/netfilter/xt_DSCP.h > # modified: include/linux/netfilter/xt_MARK.h > # modified: include/linux/netfilter/xt_RATEEST.h ... This is _exactly_ what happens if you try to develop the Linux kernel on a case-insensitive filesystem. The kernel source tree has several files that differ only in case, eg Documentation/IO-mapping.txt Documentation/io-mapping.txt include/linux/netfilter/xt_tcpmss.h include/linux/netfilter/xt_TCPMSS.h .. and if you try to check it out on a broken filesystem, then the second file will overwrite the first one, and git will think that you have modified it. OS X? Afaik, you can fix it by using NFS or UFS. And I think ZFS has a case-sensitive mode too (and it may even be the default). In fact, I think newer versions of OS X even allow that piece-of-sh*t HFS+ to be case sensitive (and thus make it much less sh*tty). Of course, there are reports of some Mac software breaking when they use a real filesystem, but hey, what else is new? 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
