On Tue, Nov 25, 2014 at 08:52:58AM +0700, Duy Nguyen wrote: > On Tue, Nov 25, 2014 at 8:23 AM, Jonathan Nieder <jrnie...@gmail.com> wrote: > > I think the biggest obstacle is the upgrade path. ;-) > > In the worst case we can always treat new repos as a different VCS. So > people will need a migration from SHA-1 to the new format, just like > they migrate from SVN/CVS to Git. Painful but simple.
Maybe we can fix the tree-sorting order while we are at it. :) More seriously, there may come a day when we are ready to break compatibility completely with a new "Git v3.0" (2.0 is already taken, of course). I do not have immediate plans for it, but it's possible that multiple factors may make such a move desirable sometime in the next 10 years, and that would be a good time to jump hash algorithms, as well. So it's possible that procrastinating on SHA-1 issues may be the least painful route. Or it may just be pushing off the day of pain. :) -Peff -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
