Hello,
Please do (and thanks for asking!).
I've done so (ticket d6d16fe1aa), but according to Richard's comment
this seems to be an issue without an (easy) fix. So we have to live with
it :)
However, as an update for others who stumble upon this, I found a (not
so magic) workaround:
1. (Temporarily) enable case sensitivity.
2. Do all necessary "A" -> "a" or "a" -> "A" renames required to
synchronize the "duplicate" file and/or folder names.
3. Commit and (if desired) disable case sensitivity again.
For me this fixed the problem for the current (and future) checkins and
the display of their contents. Of course in the "all files" view the
problem is still visible for checkins in the past, but that doesn't
bother me.
Forewarning, though: if i'm not mistaken, only a couple of the fossil
devs work on it in Windows (resp. case insensitively).
That's why we (few) Windows fossil users try to widen the test base and
report on problems we discover ;) We can verify fixes you devs cannot
test on Windows themselves.
One question though: why is "not case sensitive" the default on Windows?
Or put differently: do I have to expect any difficulties if I continue
to work with the reversed setting (which resolved my problem above and
will also help in future in case of more renames)?
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
