>be on Windows
>cloning git repo fails
>filename collisions because of case insensitive filesystem
Be on Windows
Aaron Scott
Other urls found in this thread:
cygwin.com
twitter.com
Landon Rogers
Other than understanding your frustration, I have good news for you.
cygwin.com
Go to
>Case sensitive filenames
Jason Reyes
Name 1 (one) reason why a file system should be case sensitive.
You want to have two folders inside a folder. One called Benis and the other one benis?
Oliver Hall
to avoid locales clusterfucks
Owen Hughes
>case sensitive branch names
Even if the Windows supported case sensitive filenames, it would still be most retarded idea ever.
William Murphy
Create an issue on the repo, or better a pull request renaming one of the files to an alternative that works on case-insensitive filesystems.
Whether you're working on a case-sensitive file system or not, having conflicting filenames like that in a code repo is probably an oversight.
Leo Bell
>work in a C# shop
>use git on VSTS for work control
>coworker does a bugfix, then refactors around
>notices incosistency in folder naming and fixes it so that all is in pascal case
>Visual Studio notices it as a rename
>git on the server creates a new directory with a fixed name along the prev one
>some files land in first dir, others in the second one
>nobody notices, because on their local copy all gets written in the same directory
mfw this shit happens once every quarter
Jaxon Barnes
Case sensitivity is dumb.
Ryan Ward
Because for a computer B and b are something completely different.
Lucas Walker
>having conflicting filenames like that in a code repo is probably an oversight
it's userspace of an unixy operating system
some of the conflicting filenames are base64 encoded strings