cm0002@lemmy.world to Programmer Humor · 2 days agoSomething something case-insensitive file something...lemmy.sdf.orgimagemessage-square44fedilinkarrow-up1450arrow-down122cross-posted to: [email protected]
arrow-up1428arrow-down1imageSomething something case-insensitive file something...lemmy.sdf.orgcm0002@lemmy.world to Programmer Humor · 2 days agomessage-square44fedilinkcross-posted to: [email protected]
minus-squareBatmanAoDlinkfedilinkarrow-up5·2 days 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·2 days 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-squareadr1anMlinkfedilinkarrow-up4·1 day 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-squareBatmanAoDlinkfedilinkarrow-up2·1 day 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.
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.
Sounds like a feature to me
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.