|
⇤ ← Revision 1 as of 2006-01-30 07:49:01
Size: 684
Comment:
|
Size: 715
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 8: | Line 8: |
| The standard Linux filesystems are case-sensitive, but some (like msdos) are not Almost all other UNIX filesystems are case-sensitive The OS X HFS+ filesystem is case-insensitive by default, but can be made case-sensitive All Windows filesystems are case-insensitive |
* The standard Linux filesystems are case-sensitive, but some (like msdos) are not * Almost all other UNIX filesystems are case-sensitive * The OS X HFS+ filesystem is case-insensitive by default, but can be made case-sensitive * All Windows filesystems are case-insensitive == Proposals == |
This page is to discuss the problem of interoperating between case-sensitive and case-insensitive filesystems.
The Problem
If a repository contains history for both "A" and "a", cloning it to case-insensitive filesystem will result in a collision of those history files, which will appear as corruption to verify. It will also result in collisions if both "A" and "a" appear in the same manifest.
- The standard Linux filesystems are case-sensitive, but some (like msdos) are not
- Almost all other UNIX filesystems are case-sensitive
- The OS X HFS+ filesystem is case-insensitive by default, but can be made case-sensitive
- All Windows filesystems are case-insensitive