Fossil SCM

It appears that on Windows, Fossil will "case-insensitively" 'fossil add' a file provided on the command line; however, 'fossil extras' will still list already-versioned file as extras if the file was not originally added with its exact, case-sensitive name.

Steps to reproduce:

1. Take a checked out Fossil directory on Windows.

2. Create two subdirectories inside: "Work" and "Play".

3. Create a new file in directory "Work" named "test.txt".

4. Run 'fossil extras'; it reports "Work/test.txt".

5. Run 'fossil add "work\test.txt" (noticed the lowercase "w"); it reports "ADDED work/test.txt".

6. Run 'fossil commit -m "blah"'; it does it successfully.

7. Run 'fossil extras'; it reports "Work/test.txt".

anonymous claiming to be Joerg Sonnenberger added on 2010-11-19 12:13:37: Windows is case-preserving, but case-insensitive. That means it doesn't care if you use WORK or work. Unless you explicitly iterate over the directory and use strcasecmp or so, you can't tell the difference. This easily explains the difference in behavior of "fossil extra".