Pro Tip: If you want to really annoy Windows git users, just put some on Windows “illegal characters” in the filenames before committing. It is even funnier, if the git server has no UI where it could be fixed quickly.
The filename rules are so weird, it’s not just illegal characters, sometimes the position of the character matters. I discovered a while ago that while windows has no problem with dots in filenames, for some reason they can never be the last character in the name
I imagine they rely on file extensions too much, and when they tested a file with an “empty” extension something great and terrible happened to make that rule instead of cleaning up the carnage.
Pro Tip: If you want to really annoy Windows git users, just put some on Windows “illegal characters” in the filenames before committing. It is even funnier, if the git server has no UI where it could be fixed quickly.
This should be done by default
Commit a bunch of perl cpan files with a ton of colons scattered liberally, and watch the fireworks
The filename rules are so weird, it’s not just illegal characters, sometimes the position of the character matters. I discovered a while ago that while windows has no problem with dots in filenames, for some reason they can never be the last character in the name
I imagine they rely on file extensions too much, and when they tested a file with an “empty” extension something great and terrible happened to make that rule instead of cleaning up the carnage.