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. schacon · 1790879465 · focus · HN ↗

      There are plans to keep sha1s around in a database, but as far as I know, no way to transmit those, so they seem specific to individual forges. They can be recomputed, sure, but again, any signatures break and it's possible that in the case of an actual replacement, the recomputation is now wrong and not easily comparable. So what is the point?

      1. purpleidea · 1790885403 · focus · HN ↗

         This is not about forges, it is about the repo I have in a folder on my computer. The sha1 hashes shouldn't go away. Yes the forges also need to support this.

Unofficial Hacker News client; not affiliated with Y Combinator.