Thread

1. purpleidea · 1790876403 · focus · HN ↗

   This means, if you migrate your repo, every single commit message that contains text like: "please see commit <sha1>" will now be broken.

   This will be a train wreck. I hope they don't release before adding compatibility modes to keep the existing sha1's around in the database.

   1. windsurfer · 1790878087 · focus · HN ↗

      Since SHA-1 is already broken (just expensive in terms of GPU-time), then the text "please see commit <sha1>" is also already broken.

      1. Dylan16807 · 1790878278 · focus · HN ↗

         You can't attack an existing normal commit.

         But also collisions there aren't a big deal. People will cite short hashes when referring to things and that's not "broken".

         1. windsurfer · 1790890210 · focus · HN ↗

            If it's an existing commit and you're already converting the repo, you can just convert the commit messages as well.

Unofficial Hacker News client; not affiliated with Y Combinator.