‹ BackHN Continuity

Thread

Looking forward to Git 2.56 – and 3.0

207 points · 116 comments · chmaynard

  1. globular-toast · · focus · HN ↗
    Why am I not surprised that GitHub is dragging its heels on sha256? I assume they just aren't able to change fundamental parts of their system now. So no sha256, no IPv6 etc. They can only sprinkle bits around the edges.
    1. gotosun1 · · focus · HN ↗
      It is on the horizon: <a href="https:&#x2F;&#x2F;github.com&#x2F;bk2204&#x2F;talk-rust-in-git" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;bk2204&#x2F;talk-rust-in-git uses SHA256
    2. masklinn · · focus · HN ↗
      TFA literally notes that one if the key sha256 devs is a github employee and in favor of the transition.

      And sha256 is in private preview at GitHub: <a href="https:&#x2F;&#x2F;github.com&#x2F;bk2204&#x2F;talk-rust-in-git&#x2F;blob&#x2F;dev&#x2F;presentation.adoc#one-more-thing" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;bk2204&#x2F;talk-rust-in-git&#x2F;blob&#x2F;dev&#x2F;presenta...

    3. nickserv · · focus · HN ↗
      They don&#x27;t seem to have any problems cramming in ever more AI garbage down our throats.

      Priorities!

Open on Hacker News to reply ↗

Unofficial Hacker News client; not affiliated with Y Combinator.