Thread

Git 3.0's upcoming SHA-256 default will be a costly mistake

570 points · 536 comments · chmaynard

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. oasisaimlessly · 1790876933 · focus · HN ↗
  Tools like git-filter-repo[1] support rewriting commit hashes in commit messages. git-filter-repo actually does it by default; see `--preserve-commit-hashes` in the manual[2].
  [1]: <a href="https://github.com/newren/git-filter-repo" rel="nofollow">https://github.com/newren/git-filter-repo
  [2]: <a href="https://htmlpreview.github.io/?https://github.com/newren/git-filter-repo/blob/docs/html/git-filter-repo.html" rel="nofollow">https://htmlpreview.github.io/?https://github.com/newren/git...
  1. donatj · 1790877983 · focus · HN ↗
    Sure, but that's not going to rewrite Slack messages, emails, GitHub links, docs
    diegocg · 1790878864 · focus · HN ↗
    ... do not migrate old repos? I'm not sure why people would do that. Or, if they do, why would they replace the current repo name instead of creating a different one and keeping the old one closed to make the references work.
    I don't think this is going to be a problem at all.
    hinkley · 1790932043 · focus · HN ↗
    Some companies survive longer than five years. So old repos are also active ones.

Unofficial Hacker News client; not affiliated with Y Combinator.