this post was submitted on 24 Dec 2024
393 points (95.4% liked)

Programmer Humor

19821 readers
845 users here now

Welcome to Programmer Humor!

This is a place where you can post jokes, memes, humor, etc. related to programming!

For sharing awful code theres also Programming Horror.

Rules

founded 2 years ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] UnityDevice@startrek.website 15 points 1 day ago (2 children)

The issue isn't just a simple oversight. Git includes the file name as part of the tree and commit hash. The hash has security implications. There's really no way to make the hash support case insensitivity without opening up a multitude of holes there. So there will always be a mismatch, and you can't just fix it without changing how git works from the ground up.

[–] qaz@lemmy.world 8 points 1 day ago* (last edited 1 day ago) (1 children)

Of course you can, make it lowercase internally and store the case formatted string for output.

[–] aard@kyu.de 8 points 1 day ago (1 children)

That'd break git repos where files with the same name, but different case exist.

[–] qaz@lemmy.world -2 points 1 day ago* (last edited 1 day ago)

I was talking about branch names, not file names. File duplicates due to case sensitivity aren't a problem on Windows anyway because those are already enforced by the file system. Unless you have people working on Linux that have multiple files with a similar name but with different casing but those should know better.

[–] KeenFlame@feddit.nu 1 points 1 day ago