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

It's not that simple. Git is a widely used software integrated into many places, so keeping some backwards compatibility is important.

Just going ahead and start breaking things would really be unprofessional.



They did break backwards compatibility with git v2.0 but sadly they did not bother to change the hash function.


What backwards compatibility was broken?



I'm not saying he should go out and break things now. I'm saying that the way forward he outlines could have been followed years ago, as essentially the rest of the industry did. Instead he waited until his user base was totally panicked to address their concerns.

In my view, that's not the right-- or even a rational-- way to do things.




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

Search: