Pierre-Yves Lapersonne@programming.dev to Programming@programming.dev · 3 days agoGit 3.0's upcoming SHA-256 default will be a costly mistakeblog.gitbutler.comexternal-linkmessage-square25fedilinkarrow-up196arrow-down18 cross-posted to: technology@lemmy.worldprogramming@programming.devhackernews@lemmy.bestiver.se
arrow-up188arrow-down1external-linkGit 3.0's upcoming SHA-256 default will be a costly mistakeblog.gitbutler.comPierre-Yves Lapersonne@programming.dev to Programming@programming.dev · 3 days agomessage-square25fedilink cross-posted to: technology@lemmy.worldprogramming@programming.devhackernews@lemmy.bestiver.se
minus-squarequantumvoid0@programming.devlinkfedilinkEnglisharrow-up8·edit-23 days agothats bad, i got couple of repos on sha-256, i wonder what happens if they drop it, which i think they wont, do i have to like re-create them?
minus-squareFizzyOrange@programming.devlinkfedilinkarrow-up1·edit-21 day agoIt’s too late for this to have any effect. It’s more “brace for the shitty unnecessary storm”. If you thought “main” was stupid…
minus-squarechickenf622@sh.itjust.workslinkfedilinkarrow-up18·3 days agoI don’t think they’ll drop sha256. The breaking change is that it’s now the default instead of sha1.
thats bad, i got couple of repos on sha-256, i wonder what happens if they drop it, which i think they wont, do i have to like re-create them?
It’s too late for this to have any effect. It’s more “brace for the shitty unnecessary storm”.
If you thought “main” was stupid…
I don’t think they’ll drop sha256. The breaking change is that it’s now the default instead of sha1.