Re:It is 2018 and this error message is a mistake from 1974
by smcameron on Monday June 07, 2021 @11:02PM
(#27430189)
I thought it was going to be "not a typewriter" [1] but I should have known, because 1974 is too late.
Re:It is 2018 and this error message is a mistake from 1974
by SamBam on Monday June 07, 2021 @11:02PM
(#27430179)
OS filename issues and checking in code reminds me of an 8-hour mess I got myself into due to OS X deciding that filenames are case-insensitive, and git knowing that they are not...
Re:It is 2018 and this error message is a mistake from 1974
by pezezin on Tuesday June 08, 2021 @06:14AM
(#27432706)
I have had funny experiences copying files from Linux to a NTFS partition, because NTFS is actually case-sensitive, but Windows itself is not, so you suddenly end up with two files that differ only by case and you can't delete or rename them (but funnily enough they show fine on Explorer).
Re:It is 2018 and this error message is a mistake from 1974
by psd1 on Tuesday June 08, 2021 @10:09AM
(#27435410)
Comedy. FWIW, git mv works on Windows for case-respecting renames
Re:It is 2018 and this error message is a mistake from 1974
by SamBam on Tuesday June 08, 2021 @08:31AM
(#27434253)
Yup, if I recall correctly the undeletable hidden file that git created was part of the issue.
Some years ago I was working on an embedded system that involved DisplayPort. For those unaware, DP's control channel is called AUX. One day, my new co-worker who used Windows asked me, who used Linux, why my AUX-related code wasn't checked in - which it most certainly was.
And that, folks, is how I learned about this absurd property of Windows that exists to this day.