- cross-posted to:
- programmer_humor@programming.dev
- cross-posted to:
- programmer_humor@programming.dev
You must log in or register to comment.
I’m too deep into Linux to understand this joke
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.
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.
This should be done by default
Well the windows case sensitivity is not just Bad or bad1 but also baD2 too.
Unix users think it’s bad, Bad, bAd, baD, BAd, bAD, BaD and BAD
Which bad now? Bad? BAd? BAD? or baD? bAD? or just BaD or bAd?
