You're viewing the f.duriansoftware.com public feed.

@pndcpndc@treehouse.systems
Oct 15, 2026, 9:08 PM
@zzt Those screenshots don't demonstrate what you think they do. Interestingly, they show Linus being arrogant and not as smart as he thinks he is in a completely different way.
That's the sort of output you get when git has decided that a file copy or rename has occurred and picks a "similar" file to diff against instead, resulting in an incoherent mess. Because git just can't track copies and renames, and just guesses, because that's how Linus designed it. Don't you love it when your version control system just makes stuff up? We'd call that a "hallucination" today.
💬 2🔄 1⭐ 0

Replies

@pndcpndc@treehouse.systems
Oct 15, 2026, 9:19 PM
@zzt I don't criticise Linus for coming up with that design which in retrospect turned out to have those flaws. It's elegant in its way, and works well enough most of the time, so that much is a success to be proud of. It's that he could never admit that these flaws existed and need fixing.
💬 1🔄 1⭐ 0
[object Object]zzt@mas.to
Oct 15, 2026, 9:23 PM
@pndc makes sense, thanks! I’ve edited out the screenshots til I get some better ones
💬 0🔄 0⭐ 0
Anthony "Erin" Fishingtonantonius@phpc.social
Oct 16, 2026, 12:42 AM
@pndc @zzt this reminds me of a conversation with a coworker where he was annoyed that git wasn't recognizing his file rename even though he explicitly used the cli to do it
Having just read the docs I said something like "I think it's cause git doesn't actually record rename and it basically does a heuristic to guess"
To which the only response I got was "i asked Claude and it said a bunch of crap" lol okay
💬 0🔄 1⭐ 0