@cm0002 to Programmer [email protected] • 2 months agoSomething something case-insensitive file something...lemmy.sdf.orgimagemessage-square45arrow-up1452arrow-down122cross-posted to: [email protected]
arrow-up1430arrow-down1imageSomething something case-insensitive file something...lemmy.sdf.org@cm0002 to Programmer [email protected] • 2 months agomessage-square45cross-posted to: [email protected]
minus-squaredohpaz42linkEnglish3•2 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]linkfedilink3•2 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•2 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.
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
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.
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.