‹ BackHN Continuity

Thread

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

570 points · 536 comments · chmaynard

  1. purpleidea · · 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 · · 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:&#x2F;&#x2F;github.com&#x2F;newren&#x2F;git-filter-repo" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;newren&#x2F;git-filter-repo

      [2]: <a href="https:&#x2F;&#x2F;htmlpreview.github.io&#x2F;?https:&#x2F;&#x2F;github.com&#x2F;newren&#x2F;git-filter-repo&#x2F;blob&#x2F;docs&#x2F;html&#x2F;git-filter-repo.html" rel="nofollow">https:&#x2F;&#x2F;htmlpreview.github.io&#x2F;?https:&#x2F;&#x2F;github.com&#x2F;newren&#x2F;git...

      1. okanat · · focus · HN ↗
        I need git-filter-repo to rewrite entire documentation and also resurrect and rehire earlier employees to repeat their GPG signatures.
Open on Hacker News to reply ↗

Unofficial Hacker News client; not affiliated with Y Combinator.