cm0002@lemmy.world to Programmer Humor@programming.dev · 5 months agoSomething something case-insensitive file something...lemmy.sdf.orgimagemessage-square43fedilinkarrow-up1436arrow-down121
arrow-up1415arrow-down1imageSomething something case-insensitive file something...lemmy.sdf.orgcm0002@lemmy.world to Programmer Humor@programming.dev · 5 months agomessage-square43fedilink
minus-squareBatmanAoD@programming.devlinkfedilinkarrow-up4·5 months agoIt’s not even actually that bad, at least not since January of 2020: https://stackoverflow.com/a/59687740/1858225
minus-squaredohpaz42@lemmy.worldlinkfedilinkEnglisharrow-up5arrow-down2·5 months agoThat’s called a workaround. No end user should have to rely on a workaround as a solution to a bug; and make no mistake, it’s a bug.
minus-squareadr1an@programming.devMlinkfedilinkarrow-up3·5 months agoBut whose bug is it? Really, Git origins have it tied to Linux development. Case sensitivity, or the lack thereof, on a filesystem is opinionated. That’s the real issue and is not a bug.
minus-squareBatmanAoD@programming.devlinkfedilinkarrow-up2·5 months agoMy point is that the claim in the comic and in other comments that this corrupts your repo or loses work simply isn’t true.
It’s not even actually that bad, at least not since January of 2020: https://stackoverflow.com/a/59687740/1858225
That’s called a workaround. No end user should have to rely on a workaround as a solution to a bug; and make no mistake, it’s a bug.
Sounds like a feature to me
But whose bug is it? Really, Git origins have it tied to Linux development.
Case sensitivity, or the lack thereof, on a filesystem is opinionated. That’s the real issue and is not a bug.
My point is that the claim in the comic and in other comments that this corrupts your repo or loses work simply isn’t true.