Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Except said company likely uses one of the Git forge providers, either in-house or as a SaaS, as the (oxymoronic for git) central repo. Until they support SHA-256, or the company goes with a its own git repo solution that is set up for it, companies won't make the move.


Not just git forge but probably the myriad other ancillary tools that assume SHA1




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: