Pierre-Yves Lapersonne@programming.dev to Programming@programming.dev · 24 天前Git 3.0's upcoming SHA-256 default will be a costly mistakeblog.gitbutler.comexternal-linkmessage-square25linkfedilinkarrow-up199arrow-down18 cross-posted to: technology@lemmy.worldprogramming@programming.dev
arrow-up191arrow-down1external-linkGit 3.0's upcoming SHA-256 default will be a costly mistakeblog.gitbutler.comPierre-Yves Lapersonne@programming.dev to Programming@programming.dev · 24 天前message-square25linkfedilink cross-posted to: technology@lemmy.worldprogramming@programming.dev
minus-squarequantumvoid0@programming.devlinkfedilinkEnglisharrow-up8·24 天前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?
minus-squarechickenf622@sh.itjust.workslinkfedilinkarrow-up18·24 天前I don’t think they’ll drop sha256. The breaking change is that it’s now the default instead of sha1.
minus-squareFizzyOrange@programming.devlinkfedilinkarrow-up2·22 天前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…
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?
I don’t think they’ll drop sha256. The breaking change is that it’s now the default instead of sha1.
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…