On 6/19/08, Jacob Kaplan-Moss <[EMAIL PROTECTED]> wrote: > Please don't try to turn this into a "Django should use > Git!" thread; if you do I'll just ignore you. We're not switching from > SVN any time in the foreseeable future.
I hope you are nearsighted and the foreseeable future isn't too distant. :) <!-- Ignore, nothing to see here. Really... don't even waste your time... I just can't help but think that the "network of trust" that Linus refers to in his Git talk can only help any open source project. For example, let's say you trust person X to be the source of your language updates and pull from his Git tree whenever he has a set of language updates for you. You just have to trust this one person that they'll do the right thing for that component or area of Django. That person may have others he trusts to pull merges from, and everything bubbles up to the top. This also removes any sort of special status of committers and authorizing someone as a committer. Everyone can commit to their own trees/branches, or experiment with features/fixes/updates all they want, and if it's good, someone can pull from it. You already know all the benefits of distributed SCM I'm sure. Plus, there are obviously some key infrastructure changes that would have to take place *if* Django were to switch to Git -- like Trac, for example. So even if Git is an obvious choice over SVN, the neighboring tools play a big factor as well. But I'm excited to see the "fooling around with new tech" and hope for of a Git move one day. :) --> -Rob --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
