@cm0002 to Programmer [email protected] • 1 day agoSomething something case-insensitive file something...lemmy.sdf.orgimagemessage-square43arrow-up1419arrow-down121cross-posted to: [email protected]
arrow-up1398arrow-down1imageSomething something case-insensitive file something...lemmy.sdf.org@cm0002 to Programmer [email protected] • 1 day agomessage-square43cross-posted to: [email protected]
minus-square@[email protected]linkfedilink4•1 day agoIt’s not even actually that bad, at least not since January of 2020: https://stackoverflow.com/a/59687740/1858225
minus-square@dohpaz42linkEnglish3•1 day 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-squareadr1anMlinkfedilink3•17 hours 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-square@[email protected]linkfedilink3•24 hours 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.