Fork me on GitHub

Anyone seen github do this ? You can't even have 2 folders on windows with the same name (even with different case, so this situation could never have arisen)


Some of the files are in sentilanDebugger on github, and some are in SentilanDebugger


WHen I look at the git changes, I have no pending changes at all.


look at git changes where?


you can get weird things like that when using repos on different filesystems that have different rules about that sort of thing


I'm on windows, I use git desktop to show my pending changes. It says I have none


what makes you think you should have some?


The different casing on the version on git


if the underlying filesystem is reporting the same directory for both cases, git can't tell the difference either


so is it likely if this was pulled on linux, there would indeed be 2 folders with the different case ?


If you need to use files with names in different cases, I'm pretty sure you should stick to a case-sensitive file system. NTFS, the default Windows file system, is not case sensitive by default but apparently you can put flags on separate directories. I would probably create a separate partition with a case-sensitive file system.


shit, then it would be broken on linux.


linux, or even windows on a different filesystem


How do I fix this if I'm on windows, I want git to have it all in the same folder with the proper casing


delete the folder, check it in, re-add, check it in?


that might do it, deleting the folder might show up as both folders being deleted in git


Or, figure out how to use that case-sensitive flag, enable it on all dirs within that local copy of the repo, do git status, and then git reset --hard.


there is surgery you could do on the repo using the git cli and manually creating tree objects and commits


OK, deleting removed both, and then readding got me back to one with the correct case. Bizzare, I've never dev'd on this repo (only created today) on anything other than my windows laptop. Dunno how this happened.


Unless maybe I had wrong case, checked it in, changed case and checked in again later and its picked up changes with a different folder name


some filesystems preserve case but are case insensitive


which can do that kind of thing


make it lowercase one place, uppercase somewhere else, on a case insensitive filesystem they look like the same folder, but once you move to a sensitive one you get both


"preserve case but are case insensitive" is such a terrible description, but they remember what case you used when creating a file and use that case when listing, etc, but will direct any file operations with a different case to the same file


this type of thing has been a pain with tools-build coming from depstar. Jars are case sensitive but macosx is not. depstart would copy directly from the jar into the new jar. tools-build will explod all of the jars onto the (case-insensitive) osx filesystem. so things like LICENSE and license/mit.txt could not coexist


it bit a lot of people years ago when osx popularity really took off with devs that ended up deploying on linux servers


If you're on Windows, use WSL2 and do your work there 🙂

👏 2
Martynas Maciulevičius20:02:05

Wouldn't WSL2 still run on the same NTFS? Or do they format separate partitions?


It's a separate vfs.


On my Windows laptop, using WSL2:

seanc@Sean-win-11-laptop:~$ mkdir example
seanc@Sean-win-11-laptop:~$ cd example/
seanc@Sean-win-11-laptop:~/example$ touch foo
seanc@Sean-win-11-laptop:~/example$ touch Foo
seanc@Sean-win-11-laptop:~/example$ touch FOO
seanc@Sean-win-11-laptop:~/example$ ls
FOO  Foo  foo

eccentric J21:02:07

Interestingly on OS X the default is also case-insensitive and switching to case sensitive breaks things, but I don't remember which apps specifically