3 ms·
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 sta
by AsyncAwait 10y ago
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.
- debatem1 10y agoI'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.
- snakeanus 10y agoThey did break backwards compatibility with git v2.0 but sadly they did not bother to change the hash function.
- joatmon-snoo 10y agoWhat backwards compatibility was broken?
- Kubuxu 10y agoLittle bits in CLI interface https://blogs.atlassian.com/2014/06/happened-git-2-0-full-goodies/ https://blogs.atlassian.com/2014/06/happened-git-2-0-full-go...
- deleted 10y ago[deleted]