Hacker News new | past | comments | ask | show | jobs | submit login

Why would they support it? The article clearly states it is nowhere close to being useful yet.

It is untested, unstable code that can only write to repositories and not read them.

"Much of the work to implement the SHA‑256 transition has been done, but it remains in a relatively unstable state and most of it is not even being actively tested yet. In mid-January, carlson posted the first part of this transition code, which clearly only solves part of the problem:

"First, it contains the pieces necessary to set up repositories and write _but not read_ extensions.objectFormat. In other words, you can create a SHA‑256 repository, but will be unable to read it. "




actually - i might have worded it confusingly.

For smaller projects (like my own), can i move to sha-256 with no expectation of backward compatibility today ?


"First, it contains the pieces necessary to set up repositories and write _but not read_ extensions.objectFormat. In other words, you can create a SHA‑256 repository, but will be unable to read it. "

If you want it to be write-only, sure, go ahead!




Consider applying for YC's Spring batch! Applications are open till Feb 11.

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

Search: