GIT Vulnerability

For those of you who haven't heard, there's a newly discovered vulnerability in GIT that could be an issue if a repository is compromised. You probably should update your version of it if you haven't yet.

TIL there are case insensitive filesystems in Linux. TIL there are case insensitive filesystems.

most modern file systems are better described as Case-sensitive or case-folding.

NTFS is an example of the latter while EXT3 is an example of the former.

NTFS is case sensitive in that it keeps the original casing of your file, but case insensitive in that it allows you to refer to the file using any casing. that would be case folding. compares as case insensitive but preserves original casing.

IMHO filesystems should be case sensitive (= you can only access a file by using its correct name), but should disallow creating two files with the same name but different case in a directory.
It would at least prevent those kind of problems.

That's actually a problem on my work computer.Apparently some software totally bombed the "My Documents" symlink in my %userprofile% directory, so now I have Documents (the actual documents folder), My Documents (the symlink that redirects old programs to use the Documents folder) and My Documents (a mostly empty folder that I can't delete, because reasons).
Fortunately it's not really disrupting anything, but I haven't gotten around to editing the structure to get rid of that folder, so it's always a nice reminder whenever I need to drill down to my Documents folder by hand.

You still can. As someone mentioned above, NTFS does it right: It preserves case and uses it for display, but doesn't allow you to do braindead-stupid things like having multiple files named the same except for case.

As someone mentioned above, NTFS does it right: It preserves case and uses it for display, but doesn't allow you to do braindead-stupid things like having multiple files named the same except for case.

NTFS does no such thing. It's Windows that doesn't let you actually use the case sensitivity of the file system.

that one you can*.... it's just a really stupid idea because just about every utility and program ever will go kerblammo on you if you try to do anything with a file(folder) so named

*: in some file systems anyway. it's technically legal on the EXT family of file systems IIRC but none of the drivers currently in use support it (because of how badly it makes things misbehave i think)

When you update Atlassian SourceTreealmost any windows program, it'll break the pinned icon on the taskbar.

FTFY.

Having worked on MSI modules, I know that's not an easy thing to deal with. I have found if you run the uninstall after the install (RemoveExistingProducts scheduled after InstallFinalize), the shortcut will survive. Usually. (if you change the install location during an upgrade, the shortcut will break)

Because if I wanted that I would write it like that, I don't want a FS to tell me how am I supposed to name my stuff. The same goes for programming languages.

I can't think of a language that does have reserved words.

Every platform has it quirks that are mostly by supporting legacy and I don't see any WTF in not supporting files that only differ by case in the same directory. It isn't such a big deal and the only reason you are fussing about it seems to me because the first comment you made was "I expect this shit from Microsoft"

I hear the same complaints about IE even when IE is doing something to spec. So I heard all this shit before.

I loved my 80 GB Zune. I used it to watch movies on my way to work for like 2 years until its screen broke. At the time, you could not buy a better device for watching video on the go. Apple had a model that could do it, but its battery lasted like 2/3rds of one movie.