@[email protected] to Programmer [email protected] • 3 months agoSomething something case-insensitive file something...lemmy.sdf.orgimagemessage-square43fedilinkarrow-up1437cross-posted to: [email protected]
arrow-up1437imageSomething something case-insensitive file something...lemmy.sdf.org@[email protected] to Programmer [email protected] • 3 months agomessage-square43fedilinkcross-posted to: [email protected]
minus-square@[email protected]linkfedilink4•3 months agoIt’s not even actually that bad, at least not since January of 2020: https://stackoverflow.com/a/59687740/1858225
minus-squaredohpaz42linkfedilinkEnglish5•3 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-square@[email protected]linkfedilink2•3 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.
minus-squareadr1anMlinkfedilink3•3 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.
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.
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.
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.